Loading...
Loading...
Found 6,526 Skills
Use when the user is leaving and wants work carried to completion without them — "I'm going to sleep", "work overnight", "keep working while I'm away", "I'll be offline", "don't wait for me", "don't ask, just do it", "merge it yourself", "full autonomy". Also use when a long task must survive context compaction or session death with an audit trail.
Self-evolving skills. Record user feedback, update methodologies and rules. Trigger words: update rules, record feedback, improve skill
Pasa el paso 3 de borrador a automático, después de mostrarte los números que dicen si conviene.
Orchestrate parallel subtasks across multiple repositories using vibe-kanban MCP. Use this skill when: (1) Work needs to be distributed across multiple repos, (2) Parallel execution of independent tasks is needed, (3) You need to create subtasks and collect their results, (4) Multi-agent coordination via kanban task descriptions. Triggers: "subtask", "multi-repo", "parallel tasks", "distribute work", "orchestrate".
Run a complete repository-native, spec-anchored development loop inspired by DeepSeek Harness. Use for feature development, bug fixes, simplification, architecture, process, or testing work that changes behavior, contracts, structure, test strategy, durable formats, or decision rationale; when asked to write, review, continue, implement, reject, supersede, archive, or verify a spec/Agent Note/RFC/ADR; or when code, tests, current-state docs, and decision rationale must converge in one change. Also use for read-only spec-to-code drift checks. Do not create a spec for a purely mechanical local edit that changes none of those things.
Applies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a bundled script's instructions: creating a skill, editing one, reviewing a skill change, or acting on review feedback (human or bot) about one. Not for src/, tests/, or scripts/ code.
Know a company completely. Opens by asking your goal and where your context lives (CRM? call recorder? team chat? email?), then routes to 4 modes - account deep-dive & plan (external + your internal history with them), org chart (who runs it), tech stack & wedge, competitive battlecard. Use for "tell me about <company>", "account plan for <company>", "org chart for <company>", "what's their tech stack", "battlecard for <competitor>", "how do we beat <X>", "research this account".
[user] 명시적인 작업 원천을 저장소 근거와 자연스러운 대화로 구체화해, 새 세션이나 더 낮은 수준 실행자가 원 대화 없이 사용할 수 있는 `.tigerkit/seed.md`를 준비합니다.
[user/auto] 하나의 pull request의 review feedback 또는 지원 가능한 GitHub Actions 실패를 fresh state로 읽고, 자연스러운 해결 계획을 합의한 뒤 필요 시 `seed.md`를 사용해 수정·검증·제한된 publication까지 처리합니다.
[user/auto] 사용자가 직접 해야 하는 `provisioning`, `credential`·`secret`, `login`/MFA/OTP/CAPTCHA/`passkey`, `dashboard`, `permission`, `device` `pairing`, `migration`/`cutover` 절차를 근거 기반의 자연스러운 대화로 안전하게 안내한다.