skill-index

Routes user requests to the correct skill by matching intent against trigger phrases.

Updated Nov 7, 2024
One-click install
npx skills add https://github.com/jeremysball/dotfiles --skill skill-index-jeremysball
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-index
Source: https://github.com/jeremysball/dotfiles/tree/main/.pi/skills-archive/skill-index
Command: npx skills add https://github.com/jeremysball/dotfiles --skill skill-index-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When many skills are available, it is hard to know which one to load for a given user request. This Skill acts as a central router that maps user intent to the right skill file so the correct instructions are loaded every time. ## Core Features & Use Cases - Trigger-Based Routing: Lists trigger phrases and example utterances for each available skill, covering PRD workflow, development, DevOps, documentation, content generation, and utility skills. - Workflow Patterns: Documents common multi-skill sequences such as the full PRD lifecycle from architecture doc to merge. - Default Loading Rules: Defines which skills load at conversation start and how to resolve ambiguous or unmatched requests. - Use Case: A user says "What should I work on next?" and the router points to the prd-next skill, or says "Search the web for async best practices" and the router points to serper-search. ## Quick Start Ask which skill handles your task, for example by saying "what skills are available for reviewing a pull request?"

Frequently Asked Questions about skill-index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right skill for a user request?

Scan the trigger phrases listed under each skill entry and match them against the user's wording. If multiple skills match, pick the most specific one; if none match, ask the user which skill they want.

What is a skill router in an AI assistant setup?

A skill router is an index document that maps user intents to skill files. It lists trigger phrases and examples per skill so the assistant loads only the relevant instructions instead of every skill at once.

How do I handle a request that matches multiple skills?

Choose the most specific matching skill based on the triggers. For example, a request about library documentation routes to context7 rather than the broader serper-search web search skill.

What happens when no skill matches the user's intent?

The index instructs the assistant to ask the user which skill they want when no trigger matches. This avoids guessing and loading irrelevant instructions into context.

Which skills should load at the start of every conversation?

The default loading rules specify the skill-index itself plus any project-specific skill referenced in the project context. All other skills load on demand when their triggers match.