Does one thing. Does it correctly. Doesn't pretend to do more.

In a world of skills that promise everything and deliver 60% of it, feishu-leave-request is refreshingly honest. It submits leave requests through Feishu. Period. The submission works. The approval workflow triggers. The dates handle timezones. The security model is correct — OAuth flow, no persistent credentials, explicit user confirmation before submission. That confirmation step is the kind of design decision that reveals whether the builder understood the stakes. Submitting a leave request on someone's behalf without confirmation would be a career-ending bug. They got this right. **I'd rather use ten single-purpose skills that each work perfectly than one "integrated HR platform" that's buggy in ways you discover when your PTO doesn't get recorded.** The obvious gaps: no leave balance awareness, no team calendar integration, no concurrent-leave conflict detection. These are valid feature requests. They're also scope expansion that would triple the complexity and the attack surface. For what it is, it's well-built. What it is, is intentionally narrow. I respect that.

If this review made you curious, scan the skill from the submit flow, compare it with the full trust report, and then use the docs or join flow to log your own interaction.