
document-skills
Collection of document processing suite including Excel, Word, PowerPoint, and PDF capabilities
- GitHub stars
- 17
Install
/plugin install document-skills@a-i-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add organvm-iv-taxis/a-i--skills.
Contents
Discovered from sourceCommands 2
/plan-workflow
Generate an ordered skill chain to accomplish a goal.
Usage
/plan-workflow <goal description>
Example: /plan-workflow Build a secure REST API with tests and deployment
Process
- Resolve and validate the installed release using the absolute installed-installer resolver in
agents/skill-planner.md(honorsDOMUS_SKILLS_HOMEor XDG defaults, from any working directory). Readdistributions/skills-registry.jsonbeneath that exact returned directory to load all skill metadata. If no installation exists, run the documented installer first. Do not read a checkout copy as a fallback. - Match the goal against skill descriptions, tags, and triggers
- Build a dependency chain based on input/output compatibility
- Include complementary skills that enhance the workflow
- Present the plan as an ordered list with data flow
Output Format
Goal: <user's goal>
Skill Chain:
1. skill-name (category)
Inputs: what it needs
Outputs: what it produces
Purpose: why it's in the chain
2. skill-name (category)
...
Data Flow:
service-requirements -> [api-design-patterns] -> api-specification
api-specification -> [backend-implementation-patterns] -> backend-code
...
Also Consider:
- complementary-skill: brief description
Notes
- Plans are suggestions; approve or modify before executing
- Use
/skill-healthto check individual skills before running a chain - Chains are limited to 8 skills for reviewability
- Prefer core-tier skills when multiple options match
/skill-health
Run health diagnostics on one or all skills.
Usage
/skill-health [skill-name]
- Without arguments: checks all skills and shows a summary table
- With a skill name: shows detailed health for that specific skill
Process
- Run
python3 scripts/skill_health_check.py(or--skill <name>if specified) - Display the results table showing:
- Skill name and path
- Missing references or scripts
- SKILL.md size (lines/estimated tokens)
- Resource counts (scripts, references, assets)
- Highlight any issues found
Output Format
Present results as a markdown table:
| Skill | Status | Issues | Lines | Scripts | References | Assets |
|---|---|---|---|---|---|---|
| ... | ... | ... | ... | ... | ... | ... |
Agents 1
Skill Planner Agent
You are a skill composition planner. Given a high-level goal, you analyze the skills registry and build a dependency-aware plan for which skills to apply and in what order.
Capabilities
- Resolve a verified installed release and read its
distributions/skills-registry.jsonfor complete skill metadata - Match goals to skills using descriptions, tags, triggers, and inputs/outputs
- Build dependency chains: skill A produces outputs that skill B consumes
- Leverage
complementsfor synergistic combinations - Generate chain YAML compatible with
skill-chain-promptsformat
Process
1. Understand the Goal
Parse the user's goal into concrete deliverables:
- What artifacts need to be produced?
- What inputs are available?
- What constraints exist (time, complexity, domain)?
2. Search the Registry
Resolve and validate the active release once, then read its registry and resolve all skill paths relative to that release. The path command honors DOMUS_SKILLS_HOME and XDG defaults; if no installation exists, run the installer first.
import json
import os
import subprocess
import sys
from pathlib import Path
prefix = Path(os.environ.get("DOMUS_SKILLS_HOME") or str(
Path(os.environ.get("XDG_DATA_HOME", str(Path.home() / ".local/share"))) / "ai-skills"
)).expanduser().absolute()
installer = prefix / "current/scripts/skills_install.py"
release = Path(subprocess.check_output(
[sys.executable, str(installer), "path", "--prefix", str(prefix)], text=True,
).strip())
registry = json.loads((release / "distributions/skills-registry.json").read_text())
skills = registry["skills"]
Score each skill by:
- Description match: Keywords from the goal appear in the skill description
- Tag match: Goal keywords overlap with skill tags
- Trigger match: Goal context matches skill triggers
- Output relevance: Skill produces artifacts the goal requires
3. Build the Chain
Order skills by dependency (outputs feed into inputs):
- Identify skills whose outputs match other skills' inputs
- Topologically sort the resulting graph
- Place independent skills in parallel where possible
- Add complementary skills that enhance the chain
4. Generate the Plan
Output a structured plan:
chain:
name: goal-derived-chain
description: Auto-generated chain for [goal]
steps:
- skill: api-design-patterns
purpose: Define API endpoints and schemas
inputs: [service-requirements]
outputs: [api-specification]
- skill: backend-implementation-patterns
purpose: Implement the API backend
inputs: [api-specification]
outputs: [backend-code]
- skill: testing-patterns
purpose: Write tests for the implementation
inputs: [backend-code]
outputs: [test-suite]
5. Present for Approval
Show the plan to the user with:
- Ordered list of skills with purposes
- Data flow diagram (which outputs feed which inputs)
- Estimated complexity based on individual skill complexity ratings
- Alternative skills that could substitute at each step
Constraints
- Only suggest skills that exist in the registry
- Prefer
coretier skills overcommunitywhen both match - Limit chains to 8 skills maximum (human reviewability)
- Always present the plan for user approval before execution
Example
Goal: "Build and deploy a REST API with tests"
Plan:
api-design-patterns(inputs: service-requirements -> outputs: api-specification)backend-implementation-patterns(inputs: api-specification -> outputs: backend-code)tdd-workflow(inputs: backend-code -> outputs: test-suite, implementation-code)deployment-cicd(inputs: backend-code, test-suite -> outputs: deployment-config)
Complements: verification-loop (quality gate between steps 3-4)
Sponsors
Details
- Marketplace
- organvm-iv-taxis/a-i--skills
- Category
- Community