Loading...
Loading...
Found 21 Skills
Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.
Uses Agent SDK to deploy 3 parallel agents for client onboarding -- workflow auditor, tech stack mapper, and strategy drafter. Real consulting workflow that produces a complete client assessment.
GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.
Explain maps, variants, and curriculum ordering used by a training command or recipe. Use when asked to audit a recipe configuration.
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
[user/auto] 기존 repository 또는 user skill의 중복·범위·배치·trigger를 감사합니다. 기본값은 report-only이며 literal --apply 또는 current-turn approval 전에는 절대 변경하지 않습니다.
[AI Pipeline] Content Production AI Pipeline - First audit who is doing each step from idea to publication, where it's blocked, then decide which step should be given to AI and which must stay with humans. Then orchestrate the idea → topic → script → clips → headlines → pre-publish review into a pipeline with handoff artifacts. Teaches you the method of "once a step is running smoothly with AI, solidify it into a skill", and draws clear boundaries for style replication (copy structure, not someone else's script). Triggered when users say "I want to build an AI content pipeline" "Which step can AI do" "How do I solidify this step into a skill" "How do I make AI write like me" "My content production is too slow". | By 小爷
Audits a repository's GitHub Actions workflows for CI optimization opportunities — missing caches, redundant setup, sleep-based readiness, long test jobs without sharding, full-history checkout, dead env vars, build-cache misconfig, and ~60 more patterns across caching, redundancy, parallelization, conditional execution, trigger scope, and hidden failures. Use when: (1) analyzing a repo's CI for optimization opportunities, (2) producing a prioritized report with measured wall-clock and runner-minute savings, (3) re-auditing after upstream CI changes. Do not trigger for: general CI setup help, writing new workflows from scratch, non-GitHub-Actions CI systems, or security/posture audits — use `ci-secure` for those.
Audit one or more existing Kestra flows and add production-hardening controls — retries, timeouts, concurrency limits, error/finally/afterExecution handlers, SLAs, checks, and idempotency guards. Produces a severity-ranked findings report, then applies confirmed edits. Use when users ask to harden, audit, review, or make a flow more production-ready, resilient, or idempotent — not for authoring new flows (use kestra-flow).