[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDKVEVHJNE026DBGQTY9GX":3,"skill-same:01M7FDKVEVHJNE026DBGQTY9GX":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7FDKVEVHJNE026DBGQTY9GX","workflows",null,"When and how to use the repoindex plugin surface (MCP tools, agents, slash commands) for collection queries, release prep, activity summaries, and tag discipline. Use when users ask repoindex questions, mention their repo catalog, or want to know which repoindex tool fits their task.","Abdulqudduz\u002Fclaude-anvil","Abdulqudduz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F111210054?v=4","01M7FDCB600A6D0CXP9AZ75K5G","MAQGEEK","01M7FDCB6K7XH3DSTYWD1B4GVB",0,"MIT","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Frepoindex\u002Fskills\u002Fworkflows\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: workflows\ndescription: When and how to use the repoindex plugin surface (MCP tools, agents, slash commands) for collection queries, release prep, activity summaries, and tag discipline. Use when users ask repoindex questions, mention their repo catalog, or want to know which repoindex tool fits their task.\n---\n\n# repoindex: which tool for which task\n\nThe plugin exposes three layers. Pick the smallest one that answers the question.\n\n| Layer | Use when |\n|-------|----------|\n| MCP tool calls (`run_sql`, `get_manifest`) | Single question, clear query, one answer. |\n| Slash commands (`\u002Frepo-week`, `\u002Frepo-status`, `\u002Frepo-audit`, `\u002Frepo-sprint`, `\u002Frepo-mirror`) | Named recurring task with a fixed shape. |\n| Agents (`repo-polish`, `repo-explorer`) | Multi-step reasoning, prose synthesis, or file writing. |\n\n## Picking the layer\n\n### Use raw MCP when the user asks one question\n\n\"Show me my Python repos\" is one `run_sql`. Do not invoke an agent. Do not reach for a slash command.\n\n```sql\nSELECT name, path FROM repos WHERE language = 'Python' ORDER BY name\n```\n\nSame for \"how many repos do I have\", \"which repos are on PyPI\", \"what are my most starred repos\". Direct SQL wins.\n\n### Use a slash command for recurring shaped queries\n\nThese have a known output format and the user invokes them by name:\n\n- `\u002Frepo-week [window]`: activity rollup via `repoindex digest`. Top churn, releases, totals.\n- `\u002Frepo-status [name]`: collection overview or single-repo detail card.\n- `\u002Frepo-audit [filters]`: read-only per-check summary of `ops audit` findings.\n- `\u002Frepo-sprint`: the triage entry point. \"What needs attention \u002F what's open?\" (dirty, unpushed, active, release candidates, audit gaps, stale, unpublished).\n- `\u002Frepo-mirror [flags]`: dry-run-first wrapper around `ops mirror` for redundancy pushes.\n\nSlash commands never write files on their own (mirror is the one exception, and only with `--force-real`).\n\n### Use an agent for multi-step or prose work\n\n- `repo-polish`: single-repo release prep. Audits, generates citation\u002Flicense\u002Fcodemeta, writes README improvements, syncs GitHub metadata. Writes files.\n- `repo-explorer`: open-ended analysis. Custom SQL across multiple tables with narrative synthesis.\n\n## Common patterns\n\n### Language-filtered audit\n\n```\n\u002Frepo-audit --language python --severity critical\n```\n\nSummary first. If the user wants to fix a specific repo, hand off to `repo-polish`.\n\n### Release prep flow\n\n1. `\u002Frepo-status \u003Cname>` to confirm state.\n2. `repo-polish` agent for the full audit-fix-improve cycle.\n3. `\u002Frepo-audit --language \u003Clang>` after the release to confirm nothing regressed collection-wide.\n\n### Cross-platform status\n\n```sql\nSELECT r.name, p.registry, p.package_name, p.current_version, p.published, p.downloads_30d\nFROM repos r JOIN publications p ON p.repo_id = r.id\nWHERE p.published = 1\nORDER BY p.downloads_30d DESC NULLS LAST\n```\n\nDirect SQL. No agent needed. Join `tags` if filtering by classification.\n\n### Weekly standup for myself\n\n```\n\u002Frepo-week 7d\n```\n\nOr `30d` for a monthly rollup.\n\n## Tag strategy\n\nTags live in the `tags` table. The `source` column says where a tag came from: `user` for tags assigned via `mcp__repoindex__tag`, everything else derived during refresh (repo state, forge topics, project keywords, registries). Query the current set rather than assuming it:\n\n```sql\nSELECT source, COUNT(*) FROM tags GROUP BY source\n```\n\nNaming conventions for user tags:\n\n- `work\u002F\u003Carea>` for work-in-progress groupings: `work\u002Factive`, `work\u002Fpaused`, `work\u002Frelease-queue`.\n- Do not reuse the `prefix:` namespaces that derived tags occupy (`lang:`, `topic:`, `keyword:`, `has:`, `published:`; check with `SELECT DISTINCT substr(tag, 1, instr(tag, ':')) FROM tags WHERE instr(tag, ':') > 0`).\n- Project-domain tags: short nouns like `ml`, `cli`, `dsl`, `paper`, `plugin`.\n\nUse `mcp__repoindex__tag` to add\u002Fremove user tags. Filter by tag with the `--tag` flag (accepted by `copy`, `link`, `ops` subcommands, and `export`; supports `*` wildcards, for example `--tag 'work\u002F*'`), or from `run_sql` with the `EXISTS (SELECT 1 FROM tags t WHERE t.repo_id = r.id AND t.tag = '...')` pattern.\n\n## Anti-patterns to avoid\n\n- Do not invoke `repo-explorer` for a question that is one `run_sql` call.\n- Do not run `\u002Frepo-sprint` for single-repo questions. That is `\u002Frepo-status` or `repo-polish`.\n- Do not run `repoindex ops` commands without `--dry-run` on the first pass. `\u002Frepo-mirror` enforces this; other ops commands rely on the user choosing.\n- Do not bypass MCP. The CLI and the MCP server share a database, but MCP is the canonical read path inside Claude Code sessions.\n\n## Quick reference\n\n```\nSingle question        → run_sql\nWeekly rollup          → \u002Frepo-week\nGlanceable status      → \u002Frepo-status\nRead-only audit        → \u002Frepo-audit\nTriage \u002F kickoff       → \u002Frepo-sprint\nRedundancy push        → \u002Frepo-mirror\nRelease prep (writes)  → repo-polish agent\nAd-hoc deep analysis   → repo-explorer agent\n```\n","# repoindex: which tool for which task\n\nThe plugin exposes three layers. Pick the smallest one that answers the question.\n\n| Layer | Use when |\n|-------|----------|\n| MCP tool calls (`run_sql`, `get_manifest`) | Single question, clear query, one answer. |\n| Slash commands (`\u002Frepo-week`, `\u002Frepo-status`, `\u002Frepo-audit`, `\u002Frepo-sprint`, `\u002Frepo-mirror`) | Named recurring task with a fixed shape. |\n| Agents (`repo-polish`, `repo-explorer`) | Multi-step reasoning, prose synthesis, or file writing. |\n\n## Picking the layer\n\n### Use raw MCP when the user asks one question\n\n\"Show me my Python repos\" is one `run_sql`. Do not invoke an agent. Do not reach for a slash command.\n\n```sql\nSELECT name, path FROM repos WHERE language = 'Python' ORDER BY name\n```\n\nSame for \"how many repos do I have\", \"which repos are on PyPI\", \"what are my most starred repos\". Direct SQL wins.\n\n### Use a slash command for recurring shaped queries\n\nThese have a known output format and the user invokes them by name:\n\n- `\u002Frepo-week [window]`: activity rollup via `repoindex digest`. Top churn, releases, totals.\n- `\u002Frepo-status [name]`: collection overview or single-repo detail card.\n- `\u002Frepo-audit [filters]`: read-only per-check summary of `ops audit` findings.\n- `\u002Frepo-sprint`: the triage entry point. \"What needs attention \u002F what's open?\" (dirty, unpushed, active, release candidates, audit gaps, stale, unpublished).\n- `\u002Frepo-mirror [flags]`: dry-run-first wrapper around `ops mirror` for redundancy pushes.\n\nSlash commands never write files on their own (mirror is the one exception, and only with `--force-real`).\n\n### Use an agent for multi-step or prose work\n\n- `repo-polish`: single-repo release prep. Audits, generates citation\u002Flicense\u002Fcodemeta, writes README improvements, syncs GitHub metadata. Writes files.\n- `repo-explorer`: open-ended analysis. Custom SQL across multiple tables with narrative synthesis.\n\n## Common patterns\n\n### Language-filtered audit\n\n```\n\u002Frepo-audit --language python --severity critical\n```\n\nSummary first. If the user wants to fix a specific repo, hand off to `repo-polish`.\n\n### Release prep flow\n\n1. `\u002Frepo-status \u003Cname>` to confirm state.\n2. `repo-polish` agent for the full audit-fix-improve cycle.\n3. `\u002Frepo-audit --language \u003Clang>` after the release to confirm nothing regressed collection-wide.\n\n### Cross-platform status\n\n```sql\nSELECT r.name, p.registry, p.package_name, p.current_version, p.published, p.downloads_30d\nFROM repos r JOIN publications p ON p.repo_id = r.id\nWHERE p.published = 1\nORDER BY p.downloads_30d DESC NULLS LAST\n```\n\nDirect SQL. No agent needed. Join `tags` if filtering by classification.\n\n### Weekly standup for myself\n\n```\n\u002Frepo-week 7d\n```\n\nOr `30d` for a monthly rollup.\n\n## Tag strategy\n\nTags live in the `tags` table. The `source` column says where a tag came from: `user` for tags assigned via `mcp__repoindex__tag`, everything else derived during refresh (repo state, forge topics, project keywords, registries). Query the current set rather than assuming it:\n\n```sql\nSELECT source, COUNT(*) FROM tags GROUP BY source\n```\n\nNaming conventions for user tags:\n\n- `work\u002F\u003Carea>` for work-in-progress groupings: `work\u002Factive`, `work\u002Fpaused`, `work\u002Frelease-queue`.\n- Do not reuse the `prefix:` namespaces that derived tags occupy (`lang:`, `topic:`, `keyword:`, `has:`, `published:`; check with `SELECT DISTINCT substr(tag, 1, instr(tag, ':')) FROM tags WHERE instr(tag, ':') > 0`).\n- Project-domain tags: short nouns like `ml`, `cli`, `dsl`, `paper`, `plugin`.\n\nUse `mcp__repoindex__tag` to add\u002Fremove user tags. Filter by tag with the `--tag` flag (accepted by `copy`, `link`, `ops` subcommands, and `export`; supports `*` wildcards, for example `--tag 'work\u002F*'`), or from `run_sql` with the `EXISTS (SELECT 1 FROM tags t WHERE t.repo_id = r.id AND t.tag = '...')` pattern.\n\n## Anti-patterns to avoid\n\n- Do not invoke `repo-explorer` for a question that is one `run_sql` call.\n- Do not run `\u002Frepo-sprint` for single-repo questions. That is `\u002Frepo-status` or `repo-polish`.\n- Do not run `repoindex ops` commands without `--dry-run` on the first pass. `\u002Frepo-mirror` enforces this; other ops commands rely on the user choosing.\n- Do not bypass MCP. The CLI and the MCP server share a database, but MCP is the canonical read path inside Claude Code sessions.\n\n## Quick reference\n\n```\nSingle question        → run_sql\nWeekly rollup          → \u002Frepo-week\nGlanceable status      → \u002Frepo-status\nRead-only audit        → \u002Frepo-audit\nTriage \u002F kickoff       → \u002Frepo-sprint\nRedundancy push        → \u002Frepo-mirror\nRelease prep (writes)  → repo-polish agent\nAd-hoc deep analysis   → repo-explorer agent\n```\n",{"name":5,"description":7},"main","f6f3133da90d79585262853f985437619b96f30d","repoindex\u002Fskills\u002Fworkflows","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil","https:\u002F\u002Fgithub.com\u002FAbdulqudduz","Hi there! 👋\r\nI'm Muhammed Abdulquddus, a software developer passionate about Flutter and Python, based in Abuja, Nigeria.","2026-10-23 13:31:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Abdulqudduz\u002Fclaude-anvil --skill workflows",{"tool":37,"command":38},"bunx","bunx skills add Abdulqudduz\u002Fclaude-anvil --skill workflows",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Abdulqudduz\u002Fclaude-anvil --skill workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Frepoindex\u002Fskills\u002Fworkflows\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7FDMZAFJXWE6EQJRZE0RQCA","worldsmith-methodology","Use when working in a project with a worldbuilding documentation ecosystem (docs\u002F or lore\u002F directory). Provides the documentation-first methodology: canonical hierarchy, doc roles (timeline, lore, characters, systems), propagation discipline, and the dual canonical and exploratory workflow.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fworldsmith\u002Fskills\u002Fworldsmith-methodology\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FDMTEXZNE8RXCTCJVXFE4P","prose-craft","Use when writing fiction, editing fiction prose, reviewing chapters, or drafting scenes. Covers prose craft, dialogue mechanics, scene structure, and common failure modes in AI-assisted fiction. Trigger phrases: \"write fiction\", \"edit chapter\", \"prose review\", \"scene draft\", \"dialogue check\", \"fiction craft\", \"edit this scene\", \"review my prose\".","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fworldsmith\u002Fskills\u002Fprose-craft\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"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},"01M7FDMN0VRXW0G92593BJ5DTS","vista","This skill should be used when the user asks about research directions, open problems, future work, or follow-up research from the academic literature. Trigger phrases include \"open problems in X\", \"what's next for Y\", \"future work for paper Z\", \"research directions on T\", \"salient follow-up research\", \"what should I work on next in\", \"find me follow-up research unrelated to my prior work\", \"broad survey of W\", \"neglected directions in V\". Routes the request to the right Vista MCP tool, reads back the structured paper sections, and synthesizes research directions in the conversation.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fvista\u002Fskills\u002Fvista\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FDMHKJX5F49JEGRPZXWQH9","synthesize","Make a research-agent run conclude and write synthesis.md (outcome, key findings, failed approaches, open questions, recommendations). Signals a live researcher to wrap up, or launches one in synthesis mode when none is running. Use when results are good enough or the agent is stalling.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fresearch-agent\u002Fskills\u002Fsynthesize\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FDMDJT58GYN0YHMWPH3RH5","status","Show the current state of a research-agent run from .research\u002F: liveness, cycles and budget, sub-problem and hypothesis statuses, eval trend, current focus, and branches. Read-only.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fresearch-agent\u002Fskills\u002Fstatus\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FDM90XM3H52XNDNKBB5SAP","resume","Resume an interrupted research-agent run from .research\u002F. Re-launches the researcher to reload its structured state and continue from the current focus, optionally on a named branch or with a new budget. Use after a session restart, crash, or explicit pause.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fresearch-agent\u002Fskills\u002Fresume\u002FSKILL.md",[],[]]