Add skill cache management to SDK (list, remove, validate installed skills)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 54/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- node.js, typescript
- Domain
- cli, developer-experience
Research direction
Start by reading packages/cli/src/commands/skills/validate.ts and the SDK's MpakBundleCache implementation to understand existing validation and lifecycle patterns. Add SDK methods to list, remove, and validate installed skills, then update skill validate to use the SDK. Done means each method has unit tests and the CLI uses the shared validation logic.
Written by the indexing model from the issue text.
Description
Summary
The SDK has MpakBundleCache for bundle lifecycle (list, load, remove, check updates) but no equivalent for installed skills. The CLI has skill validate and skill pack commands that operate on skill directories, but there's no SDK-level abstraction for:
- Listing installed skills — scan
~/.claude/skills/and return metadata - Removing installed skills — delete a skill directory
- Validating skill directories — check SKILL.md frontmatter, structure, naming
The validation logic currently lives in packages/cli/src/commands/skills/validate.ts and should be promoted to the SDK.
Proposed API
// New class or extension of Mpak facade
interface InstalledSkillInfo {
name: string;
path: string;
description: string;
version?: string;
}
interface SkillValidationResult {
valid: boolean;
name: string | null;
errors: string[];
warnings: string[];
}
// On the Mpak facade:
listInstalledSkills(skillsDir?: string): InstalledSkillInfo[]
removeInstalledSkill(name: string, skillsDir?: string): boolean
validateSkillDirectory(path: string): SkillValidationResult
Acceptance Criteria
- List installed skills with metadata from SKILL.md frontmatter
- Remove installed skills by name
- Validate skill directories (structure, frontmatter, naming conventions)
- Unit tests for each method
- CLI
skill validateupdated to use SDK validation
Context
Companion to #74 (installSkill). Together these give the SDK full skill lifecycle management, enabling platform consumers to manage skills without the CLI.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 13
- Avg merge
- 16m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NimbleBrainInc/mpak
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NimbleBrainInc/mpak#180 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NimbleBrainInc/mpak#175 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
NimbleBrainInc/mpak#159 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
NimbleBrainInc/mpak#120 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
NimbleBrainInc/mpak#112 ·
All issues in NimbleBrainInc/mpak
Similar issues
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Potential Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Comfy-Org/ComfyUI_frontend#23773 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lingdojo/kana-dojo#34301 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/gh-aw-firewall#11797 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#7007 ·
Maintainers usually reply within 1 day