workflows
/workflows
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.
- Author
- queelius ↗
- Repository
- claude-anvil ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Picking the layer
- Common patterns
- Tag strategy
- Anti-patterns to avoid
- Quick reference
SKILL.md preview
--- name: workflows description: 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. --- # repoindex: which tool for which task The plugin exposes three layers. Pick the smallest one that answers the question. | Layer | Use when | |-------|----------| | MCP tool calls (`run_sql`, `get_manifest`) | Single question, clear query, one answer. | | Slash commands (`/repo-week`, `/repo-status`, `/repo-audit`, `/repo-sprint`, `/repo-mirror`) | Named recurring task with a fixed shape. | | Agents (`repo-polish`, `repo-explorer`) | Multi-step reasoning, prose synthesis, or file writing. | ## Picking the layer ### Use raw MCP when the user asks one question "Show me my Python repos" is one `run_sql`. Do not invoke an agent. Do not reach for a slash command. ```sql SELECT name, path FROM repos WHERE language = 'Python' ORDER BY name ``` Same for "how many repos do I have", "which repos are on PyPI", "what are my most starred repos". Direct SQL wins. ### Use a slash command for recurring shaped queries These have a known output format and the user invokes them by name: - `/repo-week [window]`: activity rollup via `repoindex digest`. Top churn, releases, totals. - `/repo-status [name]`: collection overview or single-repo detail card. - `/repo-audit [filters]`: read-only per-check summary of `ops audit` findings. - `/repo-sprint`: the triage entry point. "What needs attention / what's open?" (dirty, unpushed, active, release candidates, audit gaps, stale, unpublished). - `/repo-mirror [flags]`: dry-run-first wrapper around `ops mirror` for redundancy pushes. Slash commands never write files on their own (mirror is the one exception, and only with `--force-real`). ### Use an agent for multi-step or prose work - `repo-polish`: single-repo release prep. Audits, generates citation/license/codemeta, writes README improvements, syncs GitHub metadata. Writes files. - `repo-explorer`: open-ended analysis. Custom SQL across multiple tables with narrative synthesis. ## Common patterns ### Language-filtered audit ``` /repo-audit --language python --severity critical ``` Summary first. If the user wants to fix a specific repo, hand off to `repo-polish`. ### Release prep flow 1. `/repo-status <name>` to confirm state. 2. `repo-polish` agent for the full audit-fix-improve cycle. 3. `/repo-audit --language <lang>` after the release to confirm nothing regressed collection-wide. ### Cross-platform status ```sql SELECT r.name, p.registry, p.package_name, p.current_version, p.published, p.downloads_30d FROM repos r JOIN publications p ON p.repo_id = r.id WHERE p.published = 1 ORDER BY p.downloads_30d DESC NULLS LAST ``` Direct SQL. No agent needed. Join `tags` if filtering by classification. ### Weekly standup for myself ``` /repo-week 7d ``` Or `30d` for a monthly rollup. ## Tag strategy Tags 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: ```sql SELECT source, COUNT(*) FROM tags GROUP BY source ``` Naming conventions for user tags: - `work/<area>` for work-in-progress groupings: `work/active`, `work/paused`, `work/release-queue`. - 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`). - Project-domain tags: short nouns like `ml`, `cli`, `dsl`, `paper`, `plugin`. Use `mcp__repoindex__tag` to add/remove user tags. Filter by tag with the `--tag` flag (accepted by `copy`, `link`, `ops` subcommands, and `export`; supports `*` wildcards, for example `--tag 'work/*'`), or from `run_sql` with the `EXISTS (SELECT 1 FROM tags t WHERE t.repo_id = r.id AND t.tag = '...')` pattern. ## Anti-patterns to avoid - Do not invoke `repo-explorer` for a question that is one `run_sql` call. - Do not run `/repo-sprint` for single-repo questions. That is `/repo-status` or `repo-polish`. - Do not run `repoindex ops` commands without `--dry-run` on the first pass. `/repo-mirror` enforces this; other ops commands rely on the user choosing. - Do not bypass MCP. The CLI and the MCP server share a database, but MCP is the canonical read path inside Claude Code sessions. ## Quick reference ``` Single question → run_sql Weekly rollup → /repo-week Glanceable status → /repo-status Read-only audit → /repo-audit Triage / kickoff → /repo-sprint Redundancy push → /repo-mirror Release prep (writes) → repo-polish agent Ad-hoc deep analysis → repo-explorer agent ```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · queelius/claude-anvil | 100 | MIT |
| phnx-labs/agi-cli | 100 | Apache-2.0 |
| CrowdStrike/fusion-skills | 100 | MIT |
| manykind-ai/plugin | 100 | MIT |
| vinnie357/claude-skills | 100 | MIT |
| vinnie357/claude-skills | 100 | MIT |
| prefecthq/prefect-mcp-server | 100 | MIT |
| danielmiessler/LifeOS | 95 | MIT |
| francoleff/Hermes-x-Google | 90 | MIT |
Database snapshot: 13.11.2026 · package version 61a416c57ddb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ac-release
Release workflow: branch, changelog, PR, tag, GH release. Triggers on keywords: release, create release, publish release, tag release - 100mcp-tool-discovery
How to discover and use MCP tools when you're unsure which one is configured. Triggers when an agent doesn't know whether an MCP tool exists for a task, or when a task description maps to multiple possible MCP servers. - 100wix-readme
What the Wix plugin holds and how to work with Wix through it: the flow the Wix MCP README returns, an index of the plugin's skills with what each does, and the Wix MCP tools with what each does. Use when the plugin was just installed or when the user asks what the Wix plugin… - 90webflow-mcp:site-activity
Query and summarize site activity logs for a Webflow enterprise site. Surfaces recent changes, identifies who made them, and generates human-readable activity reports. Use for site monitoring, change tracking, publish preparation, or weekly activity summaries. Enterprise plans only. - 100gh-tag-release
Date the changelog and push a release tag to trigger publish CI. Differs from gh-draft-release, which drafts a GitHub Release with notes. Args: none required. Use when the user asks to tag a release, publish a version, or mentions /gh-tag-release. - 100ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo. Use when the user asks which of these engineering skills or flows fits their situation. Triggers on: ask- matt, which skill should I use, what flow fits here.