[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2SAY9TCTJ051PV8HCNNGQ":3,"skill-same:01M7F2SAY9TCTJ051PV8HCNNGQ":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":12,"updatedAt":31,"install":32,"resources":45},"01M7F2SAY9TCTJ051PV8HCNNGQ","source-command-methodology-advisor",null,"Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack","313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace","313DEVGRP","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34762848?v=4","01M7F2M535Z5X8XGHYD8TDVAB3","A-RMS by 313DEVGRP","01M7F2M54CR0P3631F4YM0D014",0,"MIT","https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002F.agents\u002Fskills\u002Fsource-command-methodology-advisor\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: \"source-command-methodology-advisor\"\ndescription: \"Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack\"\n---\n\n# source-command-methodology-advisor\n\nUse this skill when the user asks to run the migrated source command `methodology-advisor`.\n\n## Command Template\n\n# Methodology Advisor\n\nAnalyze this project and recommend the best AI-assisted development methodology stack. Read what you can from the codebase first, then ask only what you cannot infer.\n\n**Time**: 2-4 minutes | **Output**: One recommended stack + contextual quick start\n\n---\n\n## Phase 1 — Silent codebase analysis\n\nRun these reads silently. Do not output results yet — build an internal picture only.\n\n### 1.1 Project identity\n\n```bash\n# Config files\ncat AGENTS.md 2>\u002Fdev\u002Fnull || cat AGENTS.md 2>\u002Fdev\u002Fnull\ncat package.json 2>\u002Fdev\u002Fnull | grep -E '\"name\"|\"description\"|\"scripts\"' | head -10\ncat Cargo.toml 2>\u002Fdev\u002Fnull | grep -E '^name|^description' | head -5\ncat pyproject.toml 2>\u002Fdev\u002Fnull | grep -E '^name|^description' | head -5\ncat go.mod 2>\u002Fdev\u002Fnull | head -3\n```\n\n### 1.2 Team size\n\n```bash\n# Unique contributors in last 90 days\ngit log --since=\"90 days ago\" --format=\"%ae\" 2>\u002Fdev\u002Fnull | sort -u | wc -l\n# Total commits\ngit log --oneline 2>\u002Fdev\u002Fnull | wc -l\n```\n\n### 1.3 Test maturity\n\n```bash\n# Test files exist?\nfind . -name \"*.test.*\" -o -name \"*.spec.*\" -o -name \"*_test.*\" -o -name \"test_*.py\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | wc -l\n# Test framework hints\ngrep -rn --include=\"*.json\" --include=\"*.toml\" --include=\"*.yaml\" \\\n  -l \"jest\\|vitest\\|pytest\\|rspec\\|mocha\\|cypress\\|playwright\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | head -5\n# CI config\nls .github\u002Fworkflows\u002F*.yml 2>\u002Fdev\u002Fnull | wc -l\nls .gitlab-ci.yml .circleci\u002Fconfig.yml 2>\u002Fdev\u002Fnull | wc -l\n```\n\n### 1.4 Spec and documentation signals\n\n```bash\n# Spec files\nfind . -name \"*.spec.md\" -o -name \"SPEC*.md\" -o -name \"spec.md\" -o -name \"DESIGN*.md\" \\\n  -o -name \"ADR*.md\" -o -name \"RFC*.md\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | head -10\n# OpenAPI \u002F contract files\nfind . -name \"openapi*.yaml\" -o -name \"openapi*.json\" -o -name \"swagger*.yaml\" \\\n  -o -name \"*.proto\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | head -5\n# BDD feature files\nfind . -name \"*.feature\" 2>\u002Fdev\u002Fnull | grep -v node_modules | wc -l\n```\n\n### 1.5 Codebase size and structure\n\n```bash\n# File count (rough)\nfind . -type f \\( -name \"*.ts\" -o -name \"*.tsx\" -o -name \"*.js\" -o -name \"*.py\" \\\n  -o -name \"*.rs\" -o -name \"*.go\" -o -name \"*.java\" -o -name \"*.rb\" \\) \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | wc -l\n# Services \u002F packages (monorepo signal)\nls packages\u002F apps\u002F services\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\n### 1.6 AI and LLM signals\n\n```bash\n# LLM API usage in code\ngrep -rn --include=\"*.ts\" --include=\"*.py\" --include=\"*.js\" \\\n  -l \"anthropic\\|openai\\|groq\\|mistral\\|langchain\\|llm\\|ChatCompletion\\|Codex\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | head -5\n# Eval framework hints\nfind . -name \"evals*\" -o -name \"*eval*\" -type d 2>\u002Fdev\u002Fnull | grep -v node_modules | head -5\n```\n\n---\n\n## Phase 2 — Score the 8 stacks\n\nUsing what you found, score each stack 0-10 based on fit signals:\n\n| Stack | Key signals that boost the score |\n|-------|----------------------------------|\n| **solo-mvp** | 1 contributor, few files, no CI yet, greenfield |\n| **team-greenfield** | 2-10 contributors, new project, no legacy files |\n| **microservices** | `packages\u002F`, `services\u002F`, OpenAPI files, `.proto` |\n| **brownfield-saas** | High commit count, large file count, few test files |\n| **enterprise-gov** | 10+ contributors, CI, ADR files, `AGENTS.md` |\n| **llm-native** | LLM imports, eval dirs, AI product signals |\n| **power-solo** | 1 contributor, high commit rate, iterative commits |\n| **plan-moderate** | Mixed signals, AGENTS.md present, moderate size |\n\n---\n\n## Phase 3 — Ask only what you cannot infer\n\nAfter the silent analysis, present your preliminary picture to the user in 2-3 lines, then ask exactly 3 questions. No more.\n\nFormat:\n\n```\nFrom your codebase I can see: [2-3 concrete observations].\nBefore recommending, 3 quick questions:\n\n1. [Pain point question — pick the most relevant from below]\n2. [Deploy frequency — if not inferable from CI\u002FCD signals]\n3. [Setup appetite — how much ceremony are you willing to invest?]\n```\n\n**Question bank — pick the 3 most relevant given what you found:**\n\n- Pain: \"What slows you down most right now — regressions, unclear requirements, context rot between sessions, or no traceability?\"\n- Pain: \"When Codex generates a large chunk of code, what is your biggest worry — quality, drift from spec, or losing track of what was built?\"\n- Deploy: \"How often do you ship to production — multiple times a day, weekly, or on longer release cycles?\"\n- Deploy: \"Is this a product with real users today, a prototype, or an internal tool?\"\n- Governance: \"How much initial setup are you willing to invest — none (just start), 30 minutes, or half a day?\"\n- Governance: \"Does anyone outside your dev team (PM, QA, compliance) need to validate what gets built?\"\n- AI product: \"Does your product expose AI-generated outputs directly to end users?\"\n- Scale: \"Do multiple services or teams need to agree on API contracts before implementing?\"\n\n---\n\n## Phase 4 — Recommendation\n\nOutput the recommendation in this structure:\n\n---\n\n### Your Stack: [Stack Name] [icon]\n\n**Why this fits your project:**\n- [Finding from Phase 1] → [explains this stack choice]\n- [Finding from Phase 1] → [explains this stack choice]\n- [Answer to question N] → [explains this stack choice]\n\n**Methodologies included:** `[Method A]` + `[Method B]` (+ `[Method C]` if applicable)\n\n**What this looks like in practice:**\n[2-3 sentences describing the concrete workflow for THIS project, using actual file names or paths found.]\n\n**Quick start for your project:**\n1. [Concrete first step using actual project context]\n2. [Second step]\n3. [Third step]\n\n**Before you start, note:**\n- [One honest trade-off or limitation of this stack]\n- [One thing to watch out for given what you found]\n\n**Go deeper:** https:\u002F\u002Fcc.bruniaux.com\u002Fmethodologies\u002F — interactive quiz and full stack comparison\n**Full methodology guide:** https:\u002F\u002Fcc.bruniaux.com\u002Fguide\u002Fmethodologies\u002F\n\n---\n\n## Stack reference (internal)\n\nUse this to map your scoring to quick-start language:\n\n**solo-mvp** (SDD + TDD): Write feature spec in AGENTS.md → `\"Write failing tests for this spec, then implement until green.\"`\n\n**team-greenfield** (Spec Kit + TDD + BDD): `\u002Fspeckit.constitution` → Given\u002FWhen\u002FThen scenarios with PM → TDD each scenario.\n\n**microservices** (CDD + Specmatic + TDD): Write OpenAPI spec first → Specmatic for contract tests → TDD implementation.\n\n**brownfield-saas** (OpenSpec + BDD + JiTTesting): OpenSpec captures current state → BDD for changed behavior → pre-merge: `\"Generate tests that catch regressions in this diff.\"`\n\n**enterprise-gov** (BMAD + Spec Kit + Specmatic): `constitution.md` → agent role definitions → Spec Kit requirements → Specmatic contract enforcement.\n\n**llm-native** (Eval-Driven + Multi-Agent): Define eval criteria (accuracy, safety, format) → build eval harness → iterate until evals pass.\n\n**power-solo** (TDD + Ralph Loop + Iterative): Tight test loop → fresh context per task via git stash + progress files → `\"Keep iterating until all tests pass and lint is clean.\"`\n\n**plan-moderate** (Plan-First + SDD + Context Engineering): Every complex task starts in Plan Mode (Shift+Tab) → validate → write spec in AGENTS.md → execute with progressive context loading.\n","# source-command-methodology-advisor\n\nUse this skill when the user asks to run the migrated source command `methodology-advisor`.\n\n## Command Template\n\n# Methodology Advisor\n\nAnalyze this project and recommend the best AI-assisted development methodology stack. Read what you can from the codebase first, then ask only what you cannot infer.\n\n**Time**: 2-4 minutes | **Output**: One recommended stack + contextual quick start\n\n---\n\n## Phase 1 — Silent codebase analysis\n\nRun these reads silently. Do not output results yet — build an internal picture only.\n\n### 1.1 Project identity\n\n```bash\n# Config files\ncat AGENTS.md 2>\u002Fdev\u002Fnull || cat AGENTS.md 2>\u002Fdev\u002Fnull\ncat package.json 2>\u002Fdev\u002Fnull | grep -E '\"name\"|\"description\"|\"scripts\"' | head -10\ncat Cargo.toml 2>\u002Fdev\u002Fnull | grep -E '^name|^description' | head -5\ncat pyproject.toml 2>\u002Fdev\u002Fnull | grep -E '^name|^description' | head -5\ncat go.mod 2>\u002Fdev\u002Fnull | head -3\n```\n\n### 1.2 Team size\n\n```bash\n# Unique contributors in last 90 days\ngit log --since=\"90 days ago\" --format=\"%ae\" 2>\u002Fdev\u002Fnull | sort -u | wc -l\n# Total commits\ngit log --oneline 2>\u002Fdev\u002Fnull | wc -l\n```\n\n### 1.3 Test maturity\n\n```bash\n# Test files exist?\nfind . -name \"*.test.*\" -o -name \"*.spec.*\" -o -name \"*_test.*\" -o -name \"test_*.py\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | wc -l\n# Test framework hints\ngrep -rn --include=\"*.json\" --include=\"*.toml\" --include=\"*.yaml\" \\\n  -l \"jest\\|vitest\\|pytest\\|rspec\\|mocha\\|cypress\\|playwright\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | head -5\n# CI config\nls .github\u002Fworkflows\u002F*.yml 2>\u002Fdev\u002Fnull | wc -l\nls .gitlab-ci.yml .circleci\u002Fconfig.yml 2>\u002Fdev\u002Fnull | wc -l\n```\n\n### 1.4 Spec and documentation signals\n\n```bash\n# Spec files\nfind . -name \"*.spec.md\" -o -name \"SPEC*.md\" -o -name \"spec.md\" -o -name \"DESIGN*.md\" \\\n  -o -name \"ADR*.md\" -o -name \"RFC*.md\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | head -10\n# OpenAPI \u002F contract files\nfind . -name \"openapi*.yaml\" -o -name \"openapi*.json\" -o -name \"swagger*.yaml\" \\\n  -o -name \"*.proto\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | head -5\n# BDD feature files\nfind . -name \"*.feature\" 2>\u002Fdev\u002Fnull | grep -v node_modules | wc -l\n```\n\n### 1.5 Codebase size and structure\n\n```bash\n# File count (rough)\nfind . -type f \\( -name \"*.ts\" -o -name \"*.tsx\" -o -name \"*.js\" -o -name \"*.py\" \\\n  -o -name \"*.rs\" -o -name \"*.go\" -o -name \"*.java\" -o -name \"*.rb\" \\) \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | wc -l\n# Services \u002F packages (monorepo signal)\nls packages\u002F apps\u002F services\u002F 2>\u002Fdev\u002Fnull | head -10\n```\n\n### 1.6 AI and LLM signals\n\n```bash\n# LLM API usage in code\ngrep -rn --include=\"*.ts\" --include=\"*.py\" --include=\"*.js\" \\\n  -l \"anthropic\\|openai\\|groq\\|mistral\\|langchain\\|llm\\|ChatCompletion\\|Codex\" \\\n  2>\u002Fdev\u002Fnull | grep -v node_modules | grep -v \".git\" | head -5\n# Eval framework hints\nfind . -name \"evals*\" -o -name \"*eval*\" -type d 2>\u002Fdev\u002Fnull | grep -v node_modules | head -5\n```\n\n---\n\n## Phase 2 — Score the 8 stacks\n\nUsing what you found, score each stack 0-10 based on fit signals:\n\n| Stack | Key signals that boost the score |\n|-------|----------------------------------|\n| **solo-mvp** | 1 contributor, few files, no CI yet, greenfield |\n| **team-greenfield** | 2-10 contributors, new project, no legacy files |\n| **microservices** | `packages\u002F`, `services\u002F`, OpenAPI files, `.proto` |\n| **brownfield-saas** | High commit count, large file count, few test files |\n| **enterprise-gov** | 10+ contributors, CI, ADR files, `AGENTS.md` |\n| **llm-native** | LLM imports, eval dirs, AI product signals |\n| **power-solo** | 1 contributor, high commit rate, iterative commits |\n| **plan-moderate** | Mixed signals, AGENTS.md present, moderate size |\n\n---\n\n## Phase 3 — Ask only what you cannot infer\n\nAfter the silent analysis, present your preliminary picture to the user in 2-3 lines, then ask exactly 3 questions. No more.\n\nFormat:\n\n```\nFrom your codebase I can see: [2-3 concrete observations].\nBefore recommending, 3 quick questions:\n\n1. [Pain point question — pick the most relevant from below]\n2. [Deploy frequency — if not inferable from CI\u002FCD signals]\n3. [Setup appetite — how much ceremony are you willing to invest?]\n```\n\n**Question bank — pick the 3 most relevant given what you found:**\n\n- Pain: \"What slows you down most right now — regressions, unclear requirements, context rot between sessions, or no traceability?\"\n- Pain: \"When Codex generates a large chunk of code, what is your biggest worry — quality, drift from spec, or losing track of what was built?\"\n- Deploy: \"How often do you ship to production — multiple times a day, weekly, or on longer release cycles?\"\n- Deploy: \"Is this a product with real users today, a prototype, or an internal tool?\"\n- Governance: \"How much initial setup are you willing to invest — none (just start), 30 minutes, or half a day?\"\n- Governance: \"Does anyone outside your dev team (PM, QA, compliance) need to validate what gets built?\"\n- AI product: \"Does your product expose AI-generated outputs directly to end users?\"\n- Scale: \"Do multiple services or teams need to agree on API contracts before implementing?\"\n\n---\n\n## Phase 4 — Recommendation\n\nOutput the recommendation in this structure:\n\n---\n\n### Your Stack: [Stack Name] [icon]\n\n**Why this fits your project:**\n- [Finding from Phase 1] → [explains this stack choice]\n- [Finding from Phase 1] → [explains this stack choice]\n- [Answer to question N] → [explains this stack choice]\n\n**Methodologies included:** `[Method A]` + `[Method B]` (+ `[Method C]` if applicable)\n\n**What this looks like in practice:**\n[2-3 sentences describing the concrete workflow for THIS project, using actual file names or paths found.]\n\n**Quick start for your project:**\n1. [Concrete first step using actual project context]\n2. [Second step]\n3. [Third step]\n\n**Before you start, note:**\n- [One honest trade-off or limitation of this stack]\n- [One thing to watch out for given what you found]\n\n**Go deeper:** https:\u002F\u002Fcc.bruniaux.com\u002Fmethodologies\u002F — interactive quiz and full stack comparison\n**Full methodology guide:** https:\u002F\u002Fcc.bruniaux.com\u002Fguide\u002Fmethodologies\u002F\n\n---\n\n## Stack reference (internal)\n\nUse this to map your scoring to quick-start language:\n\n**solo-mvp** (SDD + TDD): Write feature spec in AGENTS.md → `\"Write failing tests for this spec, then implement until green.\"`\n\n**team-greenfield** (Spec Kit + TDD + BDD): `\u002Fspeckit.constitution` → Given\u002FWhen\u002FThen scenarios with PM → TDD each scenario.\n\n**microservices** (CDD + Specmatic + TDD): Write OpenAPI spec first → Specmatic for contract tests → TDD implementation.\n\n**brownfield-saas** (OpenSpec + BDD + JiTTesting): OpenSpec captures current state → BDD for changed behavior → pre-merge: `\"Generate tests that catch regressions in this diff.\"`\n\n**enterprise-gov** (BMAD + Spec Kit + Specmatic): `constitution.md` → agent role definitions → Spec Kit requirements → Specmatic contract enforcement.\n\n**llm-native** (Eval-Driven + Multi-Agent): Define eval criteria (accuracy, safety, format) → build eval harness → iterate until evals pass.\n\n**power-solo** (TDD + Ralph Loop + Iterative): Tight test loop → fresh context per task via git stash + progress files → `\"Keep iterating until all tests pass and lint is clean.\"`\n\n**plan-moderate** (Plan-First + SDD + Context Engineering): Every complex task starts in Plan Mode (Shift+Tab) → validate → write spec in AGENTS.md → execute with progressive context loading.\n",{"name":5,"description":7},"main","f2cc95bc769ca4c3a398965b767dfb41cdf8d698","reference\u002Fclaude-code-ultimate-guide-main\u002F.agents\u002Fskills\u002Fsource-command-methodology-advisor",2,"https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace","https:\u002F\u002Fgithub.com\u002F313DEVGRP","https:\u002F\u002Fwww.a-rms.net","2026-10-18 12:48:10",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add 313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace --skill source-command-methodology-advisor",{"tool":38,"command":39},"bunx","bunx skills add 313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace --skill source-command-methodology-advisor",{"tool":41,"command":42},"pnpm","pnpm dlx skills add 313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace --skill source-command-methodology-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002F.agents\u002Fskills\u002Fsource-command-methodology-advisor\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7F343WNVHZWWYJDD77QEJ7J","voice-refine","Transform verbose voice input into structured, token-efficient Claude prompts. Use when cleaning up voice memos, dictation output, or speech-to-text transcriptions that contain filler words, repetitions, and unstructured thoughts.","https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002Fexamples\u002Fskills\u002Fvoice-refine\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7F3417SNXASFTDA1B2X4XYZ","validate-changes","Evaluate staged changes using LLM-as-a-Judge before committing","https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002Fexamples\u002Fskills\u002Fvalidate-changes\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7F33YN9QK88H2B81PVHMNG1","update-threat-db","Delegate threat-intelligence research and updates to AgentSec, then validate the guide and landing mirrors.","https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002Fexamples\u002Fskills\u002Fupdate-threat-db\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7F33SXQ57G2FVFK094T4584","token-audit","Audit Claude Code configuration to measure fixed-context token overhead and produce a prioritized action plan. Use when hitting rate limits, experiencing early context compression, or after adding significant config files.","https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002Fexamples\u002Fskills\u002Ftoken-audit\u002Fskill.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7F33NAWXFPHW59CF52EAGGK","talk-stage6-revision","Produces revision sheets with quick navigation by act, a master concept-to-URL table, Q&A cheat-sheet with 6-10 anticipated questions, glossary, and external resources list. Use when preparing for a talk with Q&A, creating shareable reference material for attendees, or building a safety-net glossary for live delivery.","https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002Fexamples\u002Fskills\u002Ftalk-pipeline\u002Fstage-6-revision\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F33G9V96HVZKAGZ84J4EBR","talk-stage5-script","Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.","https:\u002F\u002Fgithub.com\u002F313DEVGRP\u002FJava-Service-Tree-Framework-Multi-Agent-Workspace\u002Fblob\u002Fmain\u002Freference\u002Fclaude-code-ultimate-guide-main\u002Fexamples\u002Fskills\u002Ftalk-pipeline\u002Fstage-5-script\u002FSKILL.md",[],[]]