[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QPYDWRAN8JN14DPQ8PMC65":3,"skill-same:01M6QPYDWRAN8JN14DPQ8PMC65":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":14,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6QPYDWRAN8JN14DPQ8PMC65","feature-flags-architect",null,"Use when adding, retiring, or auditing feature flags. Triggers on \"add a flag\", \"ship behind a flag\", \"rollout plan\", \"kill switch\", \"stale flags\", \"flag debt\", \"LaunchDarkly\", \"GrowthBook\", \"Statsig\", \"Unleash\", \"Flipt\", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a \u002Fflag-cleanup slash command.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskills-feature-flags-architect\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"architect","feature flags","feature","feature flags architect","flags","trade-offs","cleanup","strategies","scanner","release-engineering","flipt","unleash","statsig","growthbook","launchdarkly","rollout","progressive-delivery","feature-flags","question","plan","2026-11-10 10:12:30",false,"---\nname: feature-flags-architect\ndescription: Use when adding, retiring, or auditing feature flags. Triggers on \"add a flag\", \"ship behind a flag\", \"rollout plan\", \"kill switch\", \"stale flags\", \"flag debt\", \"LaunchDarkly\", \"GrowthBook\", \"Statsig\", \"Unleash\", \"Flipt\", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a \u002Fflag-cleanup slash command.\ncontext: fork\nversion: 2.9.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [feature-flags, progressive-delivery, rollout, kill-switch, launchdarkly, growthbook, statsig, unleash, flipt, release-engineering]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Feature Flags Architect\n\nEnd-to-end discipline for feature flags: classify them, ship them, ramp them, and retire them. Most teams treat flags as throwaway `if`-statements; this skill treats them as a controlled lifecycle with measurable debt.\n\n## When to use\n\n- Adding a new flag and need a rollout plan\n- Auditing a codebase for stale or orphaned flags\n- Choosing a flag provider (LaunchDarkly vs GrowthBook vs Statsig vs Unleash vs Flipt vs build-your-own)\n- Designing a kill-switch path for a risky launch\n- Cleaning up flag debt before a release freeze\n- Reviewing whether a feature should ship behind a flag at all\n\n## Core principle: flags are a lifecycle, not an `if`\n\n```\nrequest → design → ship → ramp → cleanup → archive\n```\n\nFlags that skip cleanup become debt: dead branches, stale defaults, untested code paths, unbounded blast radius. The three scripts in this skill enforce the lifecycle.\n\n## Quick start\n\n```bash\n# 1. Audit the repo for flag debt\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90\n\n# 2. Plan a progressive rollout for a new flag\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\n\n# 3. Verify every flag has a documented kill switch\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\n```\n\n## The 4 flag types (taxonomy)\n\nDifferent flag types have different lifespans and ownership. Misclassifying creates debt.\n\n| Type | Purpose | Typical lifespan | Owner | Cleanup trigger |\n|---|---|---|---|---|\n| **Release** | Hide unfinished features in production | days–weeks | Eng | 100% rollout reached |\n| **Experiment** | A\u002FB test variants | weeks | Product\u002FMarketing | Test concluded; winner picked |\n| **Operational** | Circuit breakers, perf toggles, kill switches | months–years | Eng\u002FSRE | Replaced by autoscaling\u002Ffeature retirement |\n| **Permission** | Entitlements per user\u002Faccount\u002Fplan | years (permanent) | Product | Plan\u002Frole removed |\n\nOnly Release and Experiment flags should be on a debt-scanner watchlist. Operational and Permission flags are by design long-lived. See `references\u002Fflag_taxonomy.md` for decision tree.\n\n## The 3 Python tools\n\nAll three are stdlib-only. Run with `--help`.\n\n### `flag_debt_scanner.py`\n\nFinds flags older than `--max-age-days` with low usage, suggesting candidates for cleanup.\n\n```bash\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90 --format text\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 60 --format json > debt.json\n```\n\n**Detection heuristic:**\n1. Walk `--repo` for code references matching common flag-call patterns:\n   - `flag(\"...\")`, `isFlagEnabled(\"...\")`, `featureFlag(\"...\")`, `getFlag(\"...\")`\n   - `client.variation(\"...\", ...)`, `unleash.isEnabled(\"...\")`, `growthbook.feature(\"...\")`\n2. For each unique flag identifier, find the oldest commit that introduced it (`git log --diff-filter=A -S \u003Cname>`).\n3. Flag as DEBT if introduced > `--max-age-days` ago AND used in ≤`--min-uses` places.\n\nOutputs flag name, age in days, file references, suggested action. JSON mode is CI-friendly.\n\n### `rollout_planner.py`\n\nGenerates a phased rollout schedule from population size, target percent, duration, and strategy.\n\n```bash\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\npython scripts\u002Frollout_planner.py --population 50000 --target-percent 25 --duration-days 7 --strategy linear\npython scripts\u002Frollout_planner.py --population 1000000 --target-percent 100 --duration-days 30 --strategy log\n```\n\n**Strategies:**\n- `ring`: 1% → 5% → 25% → 50% → 100%, evenly spaced. Default for risky launches.\n- `linear`: constant rate per day. Default for medium-risk.\n- `log`: rapid early, slow tail. Default for low-risk launches with confidence.\n- `cohort`: by named cohort (internal → beta → free → paid → all).\n\nOutputs a markdown table with date, percent, expected user count, abort criteria, and verification step per phase.\n\n### `kill_switch_audit.py`\n\nCross-references code-discovered flags against documentation to verify each has a kill switch path written down.\n\n```bash\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc runbooks\u002Fflags.md --format json\n```\n\n**What it checks:**\n1. Every code-discovered flag has an entry in `--flag-doc`\n2. Each entry declares: owner, type, kill-switch trigger, monitoring dashboard\n3. Reports flags missing documentation (FAIL) or missing fields (WARN)\n\nUse as a pre-merge gate before any new flag ships.\n\n## Provider chooser (5 + DIY)\n\n| Provider | Best for | Pricing model | Lock-in risk | OSS option |\n|---|---|---|---|---|\n| **LaunchDarkly** | Enterprise, complex targeting, audit\u002Fcompliance | Per-MAU, expensive | High | No |\n| **GrowthBook** | Mid-market, A\u002FB testing focused, OSS-friendly | Per-MAU + OSS | Low | Yes (self-host) |\n| **Statsig** | Growth\u002Fproduct teams, advanced experimentation | Free tier + per-MAU | Medium | No |\n| **Unleash** | OSS-first, self-hosted, dev-friendly | OSS + Enterprise | Low | Yes |\n| **Flipt** | Lightweight, k8s-native, simple needs | OSS-only | None | Yes |\n| **DIY** | \u003C100 flags, no targeting, full control | None | None | N\u002FA |\n\nDecision rules:\n- \u003C50 flags + no targeting → DIY with config file or env vars\n- Need analytics + experimentation → Statsig or GrowthBook\n- Compliance\u002FSOC2 audit logs required → LaunchDarkly\n- Self-hosting required (data residency \u002F air-gapped) → Unleash or Flipt\n- See `references\u002Fprovider_comparison.md` for detail.\n\n## Workflows\n\n### Workflow 1: Ship a new feature behind a flag\n\n```\n1. Classify: which of the 4 flag types?\n   → Release (most common for engineering work)\n2. Run rollout_planner.py to design the ramp\n3. Add flag entry to docs\u002Ffeature-flags.md BEFORE writing code:\n   - name, owner, type, kill-switch trigger, dashboard URL\n4. Write the code with the flag\n5. Run kill_switch_audit.py — must pass before merge\n6. Deploy at 0%; verify kill switch works\n7. Execute rollout schedule; abort if abort criteria met\n8. At 100% for 7+ days: remove flag, delete dead branch, archive doc entry\n```\n\n### Workflow 2: Quarterly flag cleanup\n\n```\n1. Run flag_debt_scanner.py --repo . --max-age-days 90 > debt.md\n2. For each flagged item:\n   a. Confirm it reached 100% (or was killed)\n   b. Find the issue\u002FPR that introduced it; verify owner agrees to remove\n   c. Delete dead branches; remove flag config\n   d. Run kill_switch_audit.py — should now show one fewer flag\n3. Update CHANGELOG: \"Removed N stale flags\"\n```\n\n### Workflow 3: Choose a provider\n\n```\n1. Estimate flag count (current + 12-month projection)\n2. Required features:\n   - Targeting rules (user, account, geo, %)?\n   - A\u002FB testing + stats?\n   - Audit log \u002F SOC2?\n   - Self-hosting \u002F data residency?\n3. Pricing budget (MAU * cost-per-MAU)\n4. See provider_comparison.md decision tree\n5. Build a 30-day proof-of-concept before signing\n```\n\n### Workflow 4: Design a kill switch\n\n```\n1. Identify the failure modes:\n   - Latency spike (which threshold?)\n   - Error rate spike (which threshold?)\n   - Business metric regression (which threshold?)\n2. Wire each to an abort:\n   - Manual: dashboard link + on-call playbook\n   - Automated: alert threshold flips flag back to 0%\n3. Test the kill switch in staging BEFORE production rollout\n4. Document in flag-doc; pass kill_switch_audit.py\n```\n\n## References\n\n- `references\u002Fflag_taxonomy.md` — 4 types, decision tree, ownership, lifespan\n- `references\u002Fprovider_comparison.md` — LaunchDarkly \u002F GrowthBook \u002F Statsig \u002F Unleash \u002F Flipt \u002F DIY trade-offs\n- `references\u002Frollout_strategies.md` — ring \u002F linear \u002F log \u002F cohort \u002F geo, abort criteria, monitoring\n- `references\u002Fflag_lifecycle.md` — request → design → ship → ramp → cleanup → archive\n\n## Slash command\n\n`\u002Fflag-cleanup` — Run the full cleanup workflow on the current repo: scan for debt, generate a removal plan, audit kill switches.\n\n## Asset templates\n\n- `assets\u002Fflag_request_template.md` — fill-in form for new flag requests (name, owner, type, kill switch, rollout plan)\n\n## Anti-patterns\n\n- **Permanent flag with `if (FLAG_FOO)` 50 places** — should be a Permission flag with a runtime config, not a Release flag\n- **Flag with no owner** — when the original engineer leaves, no one cleans it up\n- **No kill switch documented** — when the feature breaks, no one knows how to disable it\n- **A\u002FB test that ran 6 months** — pick a winner; running indefinitely is debt\n- **Flags as feature toggles for cosmetic changes** — ship via deploy, not flag\n\n## Verifiable success\n\nA team using this skill should achieve:\n- 100% of new flags pass `kill_switch_audit.py` at merge time\n- `flag_debt_scanner.py --max-age-days 90` returns ≤5 stale flags repo-wide\n- Every flag has a documented owner, type, and kill switch\n- Mean time to retire a Release flag: \u003C60 days from 100% rollout\n","# Feature Flags Architect\n\nEnd-to-end discipline for feature flags: classify them, ship them, ramp them, and retire them. Most teams treat flags as throwaway `if`-statements; this skill treats them as a controlled lifecycle with measurable debt.\n\n## When to use\n\n- Adding a new flag and need a rollout plan\n- Auditing a codebase for stale or orphaned flags\n- Choosing a flag provider (LaunchDarkly vs GrowthBook vs Statsig vs Unleash vs Flipt vs build-your-own)\n- Designing a kill-switch path for a risky launch\n- Cleaning up flag debt before a release freeze\n- Reviewing whether a feature should ship behind a flag at all\n\n## Core principle: flags are a lifecycle, not an `if`\n\n```\nrequest → design → ship → ramp → cleanup → archive\n```\n\nFlags that skip cleanup become debt: dead branches, stale defaults, untested code paths, unbounded blast radius. The three scripts in this skill enforce the lifecycle.\n\n## Quick start\n\n```bash\n# 1. Audit the repo for flag debt\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90\n\n# 2. Plan a progressive rollout for a new flag\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\n\n# 3. Verify every flag has a documented kill switch\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\n```\n\n## The 4 flag types (taxonomy)\n\nDifferent flag types have different lifespans and ownership. Misclassifying creates debt.\n\n| Type | Purpose | Typical lifespan | Owner | Cleanup trigger |\n|---|---|---|---|---|\n| **Release** | Hide unfinished features in production | days–weeks | Eng | 100% rollout reached |\n| **Experiment** | A\u002FB test variants | weeks | Product\u002FMarketing | Test concluded; winner picked |\n| **Operational** | Circuit breakers, perf toggles, kill switches | months–years | Eng\u002FSRE | Replaced by autoscaling\u002Ffeature retirement |\n| **Permission** | Entitlements per user\u002Faccount\u002Fplan | years (permanent) | Product | Plan\u002Frole removed |\n\nOnly Release and Experiment flags should be on a debt-scanner watchlist. Operational and Permission flags are by design long-lived. See `references\u002Fflag_taxonomy.md` for decision tree.\n\n## The 3 Python tools\n\nAll three are stdlib-only. Run with `--help`.\n\n### `flag_debt_scanner.py`\n\nFinds flags older than `--max-age-days` with low usage, suggesting candidates for cleanup.\n\n```bash\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 90 --format text\npython scripts\u002Fflag_debt_scanner.py --repo . --max-age-days 60 --format json > debt.json\n```\n\n**Detection heuristic:**\n1. Walk `--repo` for code references matching common flag-call patterns:\n   - `flag(\"...\")`, `isFlagEnabled(\"...\")`, `featureFlag(\"...\")`, `getFlag(\"...\")`\n   - `client.variation(\"...\", ...)`, `unleash.isEnabled(\"...\")`, `growthbook.feature(\"...\")`\n2. For each unique flag identifier, find the oldest commit that introduced it (`git log --diff-filter=A -S \u003Cname>`).\n3. Flag as DEBT if introduced > `--max-age-days` ago AND used in ≤`--min-uses` places.\n\nOutputs flag name, age in days, file references, suggested action. JSON mode is CI-friendly.\n\n### `rollout_planner.py`\n\nGenerates a phased rollout schedule from population size, target percent, duration, and strategy.\n\n```bash\npython scripts\u002Frollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring\npython scripts\u002Frollout_planner.py --population 50000 --target-percent 25 --duration-days 7 --strategy linear\npython scripts\u002Frollout_planner.py --population 1000000 --target-percent 100 --duration-days 30 --strategy log\n```\n\n**Strategies:**\n- `ring`: 1% → 5% → 25% → 50% → 100%, evenly spaced. Default for risky launches.\n- `linear`: constant rate per day. Default for medium-risk.\n- `log`: rapid early, slow tail. Default for low-risk launches with confidence.\n- `cohort`: by named cohort (internal → beta → free → paid → all).\n\nOutputs a markdown table with date, percent, expected user count, abort criteria, and verification step per phase.\n\n### `kill_switch_audit.py`\n\nCross-references code-discovered flags against documentation to verify each has a kill switch path written down.\n\n```bash\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc docs\u002Ffeature-flags.md\npython scripts\u002Fkill_switch_audit.py --repo . --flag-doc runbooks\u002Fflags.md --format json\n```\n\n**What it checks:**\n1. Every code-discovered flag has an entry in `--flag-doc`\n2. Each entry declares: owner, type, kill-switch trigger, monitoring dashboard\n3. Reports flags missing documentation (FAIL) or missing fields (WARN)\n\nUse as a pre-merge gate before any new flag ships.\n\n## Provider chooser (5 + DIY)\n\n| Provider | Best for | Pricing model | Lock-in risk | OSS option |\n|---|---|---|---|---|\n| **LaunchDarkly** | Enterprise, complex targeting, audit\u002Fcompliance | Per-MAU, expensive | High | No |\n| **GrowthBook** | Mid-market, A\u002FB testing focused, OSS-friendly | Per-MAU + OSS | Low | Yes (self-host) |\n| **Statsig** | Growth\u002Fproduct teams, advanced experimentation | Free tier + per-MAU | Medium | No |\n| **Unleash** | OSS-first, self-hosted, dev-friendly | OSS + Enterprise | Low | Yes |\n| **Flipt** | Lightweight, k8s-native, simple needs | OSS-only | None | Yes |\n| **DIY** | \u003C100 flags, no targeting, full control | None | None | N\u002FA |\n\nDecision rules:\n- \u003C50 flags + no targeting → DIY with config file or env vars\n- Need analytics + experimentation → Statsig or GrowthBook\n- Compliance\u002FSOC2 audit logs required → LaunchDarkly\n- Self-hosting required (data residency \u002F air-gapped) → Unleash or Flipt\n- See `references\u002Fprovider_comparison.md` for detail.\n\n## Workflows\n\n### Workflow 1: Ship a new feature behind a flag\n\n```\n1. Classify: which of the 4 flag types?\n   → Release (most common for engineering work)\n2. Run rollout_planner.py to design the ramp\n3. Add flag entry to docs\u002Ffeature-flags.md BEFORE writing code:\n   - name, owner, type, kill-switch trigger, dashboard URL\n4. Write the code with the flag\n5. Run kill_switch_audit.py — must pass before merge\n6. Deploy at 0%; verify kill switch works\n7. Execute rollout schedule; abort if abort criteria met\n8. At 100% for 7+ days: remove flag, delete dead branch, archive doc entry\n```\n\n### Workflow 2: Quarterly flag cleanup\n\n```\n1. Run flag_debt_scanner.py --repo . --max-age-days 90 > debt.md\n2. For each flagged item:\n   a. Confirm it reached 100% (or was killed)\n   b. Find the issue\u002FPR that introduced it; verify owner agrees to remove\n   c. Delete dead branches; remove flag config\n   d. Run kill_switch_audit.py — should now show one fewer flag\n3. Update CHANGELOG: \"Removed N stale flags\"\n```\n\n### Workflow 3: Choose a provider\n\n```\n1. Estimate flag count (current + 12-month projection)\n2. Required features:\n   - Targeting rules (user, account, geo, %)?\n   - A\u002FB testing + stats?\n   - Audit log \u002F SOC2?\n   - Self-hosting \u002F data residency?\n3. Pricing budget (MAU * cost-per-MAU)\n4. See provider_comparison.md decision tree\n5. Build a 30-day proof-of-concept before signing\n```\n\n### Workflow 4: Design a kill switch\n\n```\n1. Identify the failure modes:\n   - Latency spike (which threshold?)\n   - Error rate spike (which threshold?)\n   - Business metric regression (which threshold?)\n2. Wire each to an abort:\n   - Manual: dashboard link + on-call playbook\n   - Automated: alert threshold flips flag back to 0%\n3. Test the kill switch in staging BEFORE production rollout\n4. Document in flag-doc; pass kill_switch_audit.py\n```\n\n## References\n\n- `references\u002Fflag_taxonomy.md` — 4 types, decision tree, ownership, lifespan\n- `references\u002Fprovider_comparison.md` — LaunchDarkly \u002F GrowthBook \u002F Statsig \u002F Unleash \u002F Flipt \u002F DIY trade-offs\n- `references\u002Frollout_strategies.md` — ring \u002F linear \u002F log \u002F cohort \u002F geo, abort criteria, monitoring\n- `references\u002Fflag_lifecycle.md` — request → design → ship → ramp → cleanup → archive\n\n## Slash command\n\n`\u002Fflag-cleanup` — Run the full cleanup workflow on the current repo: scan for debt, generate a removal plan, audit kill switches.\n\n## Asset templates\n\n- `assets\u002Fflag_request_template.md` — fill-in form for new flag requests (name, owner, type, kill switch, rollout plan)\n\n## Anti-patterns\n\n- **Permanent flag with `if (FLAG_FOO)` 50 places** — should be a Permission flag with a runtime config, not a Release flag\n- **Flag with no owner** — when the original engineer leaves, no one cleans it up\n- **No kill switch documented** — when the feature breaks, no one knows how to disable it\n- **A\u002FB test that ran 6 months** — pick a winner; running indefinitely is debt\n- **Flags as feature toggles for cosmetic changes** — ship via deploy, not flag\n\n## Verifiable success\n\nA team using this skill should achieve:\n- 100% of new flags pass `kill_switch_audit.py` at merge time\n- `flag_debt_scanner.py --max-age-days 90` returns ≤5 stale flags repo-wide\n- Every flag has a documented owner, type, and kill switch\n- Mean time to retire a Release flag: \u003C60 days from 100% rollout\n",{"name":5,"tags":44,"author":46,"context":47,"license":15,"version":48,"description":7,"compatible_tools":49},[36,35,34,45,33,32,31,30,29,28],"kill-switch","claude-code-skills","fork","2.9.0",[50,51,52,53,54,55],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fskills-feature-flags-architect","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill feature-flags-architect",{"tool":71,"command":72},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill feature-flags-architect",{"tool":74,"command":75},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill feature-flags-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskills-feature-flags-architect\u002FSKILL.md",true,[],[80,112,136,163,188,212],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":91,"publishedAt":39},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":39},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[119,120,121,122,96,123,124,38,125,126,127,128,129,130,131,132,133,134,135,108],"twitter","x twitter growth","growth","research","content","engineering","web search","competitors","analyze","engine","write","strategy","use","platform","grow","posting","competitive",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":145,"publishedAt":39},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发",[146,129,147,148,149,150,151,152,131,153,154,56,155,156,157,158,159,160,161,162],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":39},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[170,171,172,173,174,175,176,177,178,131,179,103,180,181,182,183,184,185,186,187],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":39},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[194],{"categoryNo":143,"categoryName":144,"taxonomyType":89,"taxonomyTypeDesc":90},[196,197,198,199,200,148,175,201,202,203,204,205,129,206,102,207,208,209,210,211],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":39},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[219,220,221,222,223,224,225,226,227,204,228,229,27,230,231,232,104,233,234,187],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","conversation","back","project","sprint","cadence"]