[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB360ZQ0231NX2QYWVRPKP":3,"skill-same:01M7AB360ZQ0231NX2QYWVRPKP":54},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AB360ZQ0231NX2QYWVRPKP","sonarclaude",null,"Query SonarCloud API for code quality data. Use when: checking quality gate status, fetching code issues or security hotspots, reviewing metrics (coverage, bugs, code smells), or the user says \"sonar\", \"quality gate\", \"code quality\", \"sonarclaude\".","agentculture\u002Fculture-nodes","agentculture","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277824871?v=4","01M7AAZDPCFA8RDCA27DQKKWCJ","AgentCulture","01M7AAZDQ1B6FYE24021YCDAPR",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsonarclaude\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sonarclaude\ntype: command\ndescription: >\n  Query SonarCloud API for code quality data. Use when: checking quality gate status,\n  fetching code issues or security hotspots, reviewing metrics (coverage, bugs, code smells),\n  or the user says \"sonar\", \"quality gate\", \"code quality\", \"sonarclaude\".\n---\n\n# SonarClaude\n\nQuery SonarCloud projects for quality gate status, issues, metrics, and security hotspots.\n\n## Prerequisites\n\nThe script requires the following tools on `PATH`:\n\n- `bash`\n- `curl` — talks to the SonarCloud REST API\n- `jq` — parses responses and URL-encodes accept comments\n\n## Environment\n\nRequires `SONAR_TOKEN` environment variable. Set the project key per-repo via\nthe `SONAR_PROJECT` environment variable (or pass `--project KEY` on each\ninvocation).\n\n## Usage\n\n```bash\n# Quality gate status (pass\u002Ffail)\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh status\n\n# List issues (bugs, vulnerabilities, code smells)\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues\n\n# Filter issues by severity and type\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues --severity CRITICAL --type BUG\n\n# Key metrics (coverage, bugs, code smells, duplication, LOC)\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh metrics\n\n# Security hotspots\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh hotspots\n\n# Accept (won't-fix) an OPEN issue with a rationale comment\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh accept \\\n  --issue AZ3Ep83i4ywi8V_l99p0 \\\n  --comment \"Pushback: rule premise doesn't fit our test fixture pattern.\"\n\n# Different project\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh status --project OtherOrg_OtherProject\n\n# Raw JSON output\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues --raw\n\n# Limit results\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues --limit 10\n```\n\n## Options\n\n| Flag | Default | Description |\n|------|---------|-------------|\n| `--project` | `$SONAR_PROJECT` | SonarCloud project key |\n| `--severity` | all | Filter: `BLOCKER`, `CRITICAL`, `MAJOR`, `MINOR`, `INFO` |\n| `--type` | all | Filter: `BUG`, `VULNERABILITY`, `CODE_SMELL` |\n| `--limit` | `25` | Max results returned |\n| `--raw` | off | Output raw JSON instead of formatted summary |\n| `--issue` | — | Issue key (required for `accept`) |\n| `--comment` | — | Rationale comment (required for `accept`) |\n\n## When to use `accept`\n\nSonar rules occasionally flag patterns where the rule's premise does not fit the\ncode (e.g. test fixtures with intentional bad-password literals, contradictory\nrule pairs like S7494 vs S7500). After deciding pushback in PR review, run\n`sonar.sh accept` with a rationale comment instead of leaving the issue OPEN —\nthis moves it to ACCEPTED\u002FWONTFIX in SonarCloud history (visible to future\nmaintainers) while clearing the quality-gate signal. Always include a `--comment`\nexplaining why; silent dismissals are not acceptable curation.\n\nDo not call SonarCloud's HTTP API directly from other skills or one-off\nscripts — `sonar.sh accept` is the supported entry point so the rationale\nflow stays consistent.\n","# SonarClaude\n\nQuery SonarCloud projects for quality gate status, issues, metrics, and security hotspots.\n\n## Prerequisites\n\nThe script requires the following tools on `PATH`:\n\n- `bash`\n- `curl` — talks to the SonarCloud REST API\n- `jq` — parses responses and URL-encodes accept comments\n\n## Environment\n\nRequires `SONAR_TOKEN` environment variable. Set the project key per-repo via\nthe `SONAR_PROJECT` environment variable (or pass `--project KEY` on each\ninvocation).\n\n## Usage\n\n```bash\n# Quality gate status (pass\u002Ffail)\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh status\n\n# List issues (bugs, vulnerabilities, code smells)\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues\n\n# Filter issues by severity and type\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues --severity CRITICAL --type BUG\n\n# Key metrics (coverage, bugs, code smells, duplication, LOC)\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh metrics\n\n# Security hotspots\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh hotspots\n\n# Accept (won't-fix) an OPEN issue with a rationale comment\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh accept \\\n  --issue AZ3Ep83i4ywi8V_l99p0 \\\n  --comment \"Pushback: rule premise doesn't fit our test fixture pattern.\"\n\n# Different project\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh status --project OtherOrg_OtherProject\n\n# Raw JSON output\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues --raw\n\n# Limit results\nbash .claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh issues --limit 10\n```\n\n## Options\n\n| Flag | Default | Description |\n|------|---------|-------------|\n| `--project` | `$SONAR_PROJECT` | SonarCloud project key |\n| `--severity` | all | Filter: `BLOCKER`, `CRITICAL`, `MAJOR`, `MINOR`, `INFO` |\n| `--type` | all | Filter: `BUG`, `VULNERABILITY`, `CODE_SMELL` |\n| `--limit` | `25` | Max results returned |\n| `--raw` | off | Output raw JSON instead of formatted summary |\n| `--issue` | — | Issue key (required for `accept`) |\n| `--comment` | — | Rationale comment (required for `accept`) |\n\n## When to use `accept`\n\nSonar rules occasionally flag patterns where the rule's premise does not fit the\ncode (e.g. test fixtures with intentional bad-password literals, contradictory\nrule pairs like S7494 vs S7500). After deciding pushback in PR review, run\n`sonar.sh accept` with a rationale comment instead of leaving the issue OPEN —\nthis moves it to ACCEPTED\u002FWONTFIX in SonarCloud history (visible to future\nmaintainers) while clearing the quality-gate signal. Always include a `--comment`\nexplaining why; silent dismissals are not acceptable curation.\n\nDo not call SonarCloud's HTTP API directly from other skills or one-off\nscripts — `sonar.sh accept` is the supported entry point so the rationale\nflow stays consistent.\n",{"name":5,"type":24,"description":7},"command","main","a2056e6191a4e106faf886773efed2f44ff120b2",".claude\u002Fskills\u002Fsonarclaude",0,"https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes","https:\u002F\u002Fgithub.com\u002Fagentculture","https:\u002F\u002Fagentculture.org","Agent first OSS software","2026-09-29 08:50:58",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add agentculture\u002Fculture-nodes --skill sonarclaude",{"tool":40,"command":41},"bunx","bunx skills add agentculture\u002Fculture-nodes --skill sonarclaude",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agentculture\u002Fculture-nodes --skill sonarclaude","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsonarclaude\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fsonar.sh","SCRIPT","脚本",8019,"https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsonarclaude\u002Fscripts\u002Fsonar.sh",[55,62,67,72,79,86],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AB6FGWR0P3SPYFX2W801D5","sample","Fixture skill proving the .qwen\u002Fskills leg carries at least one skill.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002Fadapters\u002Fqwen\u002Ftests\u002Ffixtures\u002Fconfig-repo-no-culture-yaml\u002F.qwen\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":63,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AB6E9PFCDZE193CGPM0K35","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002Fadapters\u002Fqwen\u002Ftests\u002Ffixtures\u002Fconfig-repo-no-agents-md\u002F.qwen\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":68,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AB6CJ3G1ZZJD63NEZZK1JH","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002Fadapters\u002Fqwen\u002Ftests\u002Ffixtures\u002Fconfig-repo-complete\u002F.qwen\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AB64WWKV9H2J7JDV5KXGPA","think","Think a vague feature idea into a buildable spec by working backwards (the idea→spec leg; drives the `devague` CLI). Start from the announcement (\"pretend it shipped\"), capture and classify claims, interrogate them with honesty conditions and hard questions, park open vagueness as a first-class object, and export a spec only once the frame *converges*. Use when the user says \"think this through\", \"spec this\", \"work backwards\", \"turn this idea into a spec\", \"announcement frame\", or \"devague\", or when a feature request is too vague to build yet. Explore scope first when the idea touches an existing codebase — the sibling `scope` skill is the optional opening leg ahead of `think`. Once a spec exports, hand off to the sibling `spec-to-plan` skill to turn it into a plan. Authored and maintained in agentculture\u002Fdevague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fthink\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AB5X0FTZ081AFH3BTGQKVA","summarize-delivery","Close the loop after an `assign-to-workforce` run by turning what actually happened into an accountability artifact — planned versus actual delivery, mid-work decisions, plan drift, evidence-backed delivery claims, and remaining work. The plan the user confirmed is the contract; this skill records where execution obeyed it, where it changed, and what is genuinely safe to claim as delivered. Runs on complete, partial, AND failed runs — failure is reported faithfully, never smoothed over. Use when the user says \"summarize delivery\", \"delivery summary\", \"wrap up\", \"close the loop\", \"what did we actually ship\", or \"plan versus actual\", or after `assign-to-workforce` merges (or fails to merge) a plan's waves. Authored and maintained in agentculture\u002Fdevague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the inbound skills here.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fsummarize-delivery\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AB5NA0QY9NN076N24NJPJQ","spec-to-plan","Turn a converged devague spec into a buildable plan by working forwards (the spec→plan leg; drives the `devague plan` CLI group). Seed a plan from a converged frame, add tasks that collectively cover every coverage target (the frame's confirmed claims + honesty conditions), give each task acceptance criteria and an honest dependency order, park genuine unknowns as first-class risks, and export a plan only once it *converges*. Use when the user says \"spec to plan\", \"stp\", \"turn this spec into a plan\", \"plan this spec\", \"make a build plan\", or after the `think` skill exports a spec. Authored and maintained in agentculture\u002Fdevague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.","https:\u002F\u002Fgithub.com\u002Fagentculture\u002Fculture-nodes\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fspec-to-plan\u002FSKILL.md",[],[]]