Skill Router for Standalone Installs
Read ~/.config/theprawnskills/library.json and use its library path as the
repository root. If absent and this skill is a symlink, resolve it to locate
the clone. For a copied installation, inspect the intended clone and repair
the pointer through the installer; the installed copy is not the library.
The repo root contains default-profile.toml and skills/.
Read <root>/platforms/linux/README.md for platform conventions. Search names
and descriptions with rg in <root>/skills and <root>/platforms/linux/skills.
Choose the smallest relevant set, prefer a standalone variant when present, and
read each selected SKILL.md fully before acting. Resolve symlinks before
following relative references. Never install the full library just to search it.
| Request |
Starting points |
| API compatibility and serialized provider/consumer contracts |
api-contracts; openapi-to-typescript for generated types |
| Understand an unfamiliar repository |
codebase-onboarding; codebase-design for choosing changes |
| Record or find architectural decisions and rationale |
architecture-decision-records; cross-harness-state for current task state |
| Bounded repair loops, agent roles, terminal/worktree coordination |
bounded-agent-loop, cli-agent-router |
| Create, add, update, audit, remove skills |
Standalone variants of skill-create, skill-add, skill-update, skill-cleanup, skill-remove, skill-authoring |
| Coding, review, debugging |
build, check, refactor, requesting-code-review, systematic-debugging |
| Completion evidence across build/types/lint/tests |
verification-loop; check remains SPEC drift only |
| Python testing; React component testing; browser flows |
python-testing; react-testing; webapp-testing |
| Pi-hole, resolver health and Tailscale DNS routing |
homelab-pihole-dns, docker-expert |
| Visual explanations, diagrams, UML/C4, flows, comparisons, HTML reports |
visual-explainer; postplan-upload for hosted delivery |
| Documents, spreadsheets, presentations |
pdf, docx, xlsx, pptx |
| Frontend design |
frontend-design, web-design-guidelines, shadcn |
| Cloudflare |
cloudflare, wrangler, workers-best-practices |
| Azure / Supabase / Vercel |
azure-prepare, supabase, deploy-to-vercel |
| Images, video, audio |
ai-image-generation, image-to-video, text-to-speech |
| Writing and marketing |
technical-blog-writing, case-study-writing, content-repurposing |
| Session continuity across agents |
cross-harness-state; session-handoff; molt |
| Repo standardization and compliance |
repo-standardization; shell |
Verify candidate availability and tool prerequisites from the actual files.
Keep source skills and installed links/copies separate. Use the Python installer
for local exposure, and do not run OneDrive propagation or dotagents sync.
Keep visual-explainer in the daily profile with postplan-upload. Use its
shared dark/cyan template whenever a visual helps, including short answers.
The document order is visual overview, details, next steps. Hosting is a
separate delivery step governed by the user's authorization.
1---2name: skill-router-23description: >-4 Find and load on-demand skills from a Prawn Skills Git clone on any supported OS.5 Use for unfamiliar tooling, specialized tasks, skill discovery, or requests6 involving documents, media, cloud platforms, writing, or skill maintenance.7license: MIT8metadata:9 source: https://skillmd.com/skills/hongyime/skill-router-210 platform: "Codex, Antigravity (agy), OpenCode, Muse on Windows, macOS, Linux (Debian)"11---1213# Skill Router for Standalone Installs1415Read `~/.config/theprawnskills/library.json` and use its `library` path as the16repository root. If absent and this skill is a symlink, resolve it to locate17the clone. For a copied installation, inspect the intended clone and repair18the pointer through the installer; the installed copy is not the library.19The repo root contains `default-profile.toml` and `skills/`.2021Read `<root>/platforms/linux/README.md` for platform conventions. Search names22and descriptions with `rg` in `<root>/skills` and `<root>/platforms/linux/skills`.23Choose the smallest relevant set, prefer a standalone variant when present, and24read each selected `SKILL.md` fully before acting. Resolve symlinks before25following relative references. Never install the full library just to search it.2627| Request | Starting points |28|---|---|29| API compatibility and serialized provider/consumer contracts | api-contracts; openapi-to-typescript for generated types |30| Understand an unfamiliar repository | codebase-onboarding; codebase-design for choosing changes |31| Record or find architectural decisions and rationale | architecture-decision-records; cross-harness-state for current task state |32| Bounded repair loops, agent roles, terminal/worktree coordination | bounded-agent-loop, cli-agent-router |33| Create, add, update, audit, remove skills | Standalone variants of skill-create, skill-add, skill-update, skill-cleanup, skill-remove, skill-authoring |34| Coding, review, debugging | build, check, refactor, requesting-code-review, systematic-debugging |35| Completion evidence across build/types/lint/tests | verification-loop; check remains SPEC drift only |36| Python testing; React component testing; browser flows | python-testing; react-testing; webapp-testing |37| Pi-hole, resolver health and Tailscale DNS routing | homelab-pihole-dns, docker-expert |38| Visual explanations, diagrams, UML/C4, flows, comparisons, HTML reports | visual-explainer; postplan-upload for hosted delivery |39| Documents, spreadsheets, presentations | pdf, docx, xlsx, pptx |40| Frontend design | frontend-design, web-design-guidelines, shadcn |41| Cloudflare | cloudflare, wrangler, workers-best-practices |42| Azure / Supabase / Vercel | azure-prepare, supabase, deploy-to-vercel |43| Images, video, audio | ai-image-generation, image-to-video, text-to-speech |44| Writing and marketing | technical-blog-writing, case-study-writing, content-repurposing |45| Session continuity across agents | cross-harness-state; session-handoff; molt |46| Repo standardization and compliance | repo-standardization; shell |4748Verify candidate availability and tool prerequisites from the actual files.49Keep source skills and installed links/copies separate. Use the Python installer50for local exposure, and do not run OneDrive propagation or `dotagents sync`.5152Keep `visual-explainer` in the daily profile with `postplan-upload`. Use its53shared dark/cyan template whenever a visual helps, including short answers.54The document order is visual overview, details, next steps. Hosting is a55separate delivery step governed by the user's authorization.