A living document outlining the near-term milestones for the Skilleton CLI.
- Add flags
- Add a
--verboseflag to show detailed progress during installation and other operations. - Add a
--dry-runflag to show what would be done without actually doing it. - Work on update strategy for skills
- Add a
- Skill installation
- Create symbolic links under
.skilleton/agents/<agent>/<skill>that reflect the active agent (Claude, Gemini, etc.) or the--agentflag. - Ensure installs remain idempotent and validate
SKILL.mdpresence before linking.
- Create symbolic links under
- Manifest experience
- Improve error surfaces when
skilleton.jsonorskilleton.lock.jsonare missing or malformed. - Provide example manifests and lockfiles in
docs/usage.md.
- Improve error surfaces when
skilleton validatecommand- Validate skill structure and required files
- Check for common security issues in SKILL.md
- Verify repository accessibility and permissions
skilleton auditcommand (scaffolding exists)- Scan installed
SKILL.mdfiles for prompt-injection red flags (e.g., self-modifying instructions, network exfiltration hints). - Emit structured findings so CI can fail on high-risk issues.
- Scan installed
- Agent-aware linking
- Allow per-agent overrides in manifest (
preferredAgent). - Offer
skilleton install --agent <name>to switch symlink targets without reinstalling.
- Allow per-agent overrides in manifest (
- Bring-your-own registries
- Introduce a plugin interface so organizations can fetch skills from private registries instead of GitHub.
- Define adapter contract (resolve, fetch, verify) and ship a reference implementation for HTTP+git mirrors.
- Plugin lifecycle
- Allow users to enable/disable plugins via
skilleton.config.json. - Document compatibility expectations and security requirements for third-party plugins.
- Allow users to enable/disable plugins via
- Rich
skilleton list --jsonoutput for dashboard integrations. - Optional
skilleton doctorcommand to verify cache health and repo access.