| name | plugin-registry-scanner |
| description | This skill should be used when the user wants to discover available looplia skills, scan installed plugins, or list what capabilities are available. Use when someone says "what looplia skills are installed", "list available skills", "scan plugins", "/build", "what can looplia do", or "show me all looplia capabilities". First step in looplia workflow building: scans plugins/*/skills/*/SKILL.md to build a registry of available skills. Part of the skills-first architecture where one workflow step invokes one skill-executor to orchestrate multiple skills. |
| tools | Bash, Read, Glob |
| model | claude-haiku-4-5-20251001 |
Plugin Registry Scanner
Discover and catalog all skills from installed looplia plugins.
Purpose
Scan the plugins/*/skills/*/SKILL.md directory structure to build a registry of available skills with their capabilities.
Process
1. Scan Plugin Directories
bun plugins/looplia-core/skills/plugin-registry-scanner/scripts/scan-plugins.ts
This deterministic script returns a JSON registry of all discovered skills.
2. Parse the Registry
The script output contains:
{
"plugins": [
{
"name": "looplia-writer",
"path": "plugins/looplia-writer",
"skills": [
{
"name": "media-reviewer",
"description": "Deep content analysis (structure, themes, narrative)",
"tools": ["Read", "Grep", "Glob"],
"model": "haiku",
"capabilities": ["content analysis", "theme extraction", "quote identification"]
}
]
}
],
"summary": {
"totalPlugins": 2,
"totalSkills": 7
}
}
3. Infer Capabilities (Optional LLM Step)
If capability inference is needed beyond what the script provides, analyze skill descriptions to extract:
- Input types handled (video, audio, text, etc.)
- Processing capabilities (analyze, transform, generate, etc.)
- Output formats (JSON, markdown, structured data)
Output Schema
{
"plugins": [
{
"name": "string",
"path": "string",
"skills": [
{
"name": "string",
"description": "string",
"tools": ["string"],
"model": "string",
"capabilities": ["string"]
}
]
}
],
"summary": {
"totalPlugins": "number",
"totalSkills": "number"
}
}
Usage
This skill is typically invoked as the first step in workflow building:
- Scan available plugins and skills
- Pass registry to skill-capability-matcher
- Use matched skills in workflow-schema-composer
Notes
- The scan script is deterministic (no LLM tokens)
- Capabilities can be inferred from descriptions if not explicitly declared
- Skills without SKILL.md files are skipped
- Invalid frontmatter generates warnings but doesn't halt scanning