Agent skill · AI & Agents

kirby-project-tour

Maps a Kirby project using Kirby MCP tools/resources, including roots, templates, snippets, controllers, models, blueprints, plugins, runtime status, and key config. Use when a user wants a project overview, file locations, or a quick orientation before making changes.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill kirby-project-tour-bnomei-kirby-mcp --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/analysis/kirby-project-tour-bnomei-kirby-mcp/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Kirby Project Tour ## Quick start - Follow the workflow below for a structured tour. ## KB entry points - `kirby://kb/glossary/roots` - `kirby://kb/glossary/template` - `kirby://kb/glossary/controller` - `kirby://kb/glossary/blueprint` - `kirby://kb/glossary/plugin` ## Required inputs - Focus area (Panel, frontend, performance, security). - Desired depth and output format. - Any known pain points to prioritize. ## Output template - Roots: templates, snippets, controllers, models, blueprints, content, config, plugins. - Inventory: templates/snippets/controllers/models/blueprints/plugins counts and notable overrides. - Config highlights: debug/cache/routes/languages. - Risks or gaps: missing runtime, unknown plugins, stale blueprints. - Next steps: 3 targeted recommendations (DX/perf/security). ## First edits - Content display tweaks: `site/templates` and `site/snippets`. - Query logic: `site/controllers`. - Panel schema: `site/blueprints`. ## Common pitfalls - Reporting locations without reading `kirby://roots`. - Skipping runtime install when indexes look empty. ## Workflow 1. Call `kirby:kirby_init` to capture versions and composer audit details. 2. Read `kirby://roots` and summ

What's inside
Steps it walks through
  1. Quick start
  2. KB entry points
  3. Required inputs
  4. Output template
  5. First edits
  6. Common pitfalls
  7. Workflow
  8. Output checklist
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the kirby-project-tour skill do?

Maps a Kirby project using Kirby MCP tools/resources, including roots, templates, snippets, controllers, models, blueprints, plugins, runtime status, and key config. Use when a user wants a project overview, file locations, or a quick orientation before making changes.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill kirby-project-tour-bnomei-kirby-mcp --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going