Add packSkill() to SDK for building .skill bundles programmatically
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- cli, developer-experience
Research direction
Read packages/cli/src/commands/skills/pack.ts to understand the existing pack flow, then inspect the SDK validation work described in issue #75. The issue calls for an SDK API that validates a skill directory, creates a .skill ZIP bundle, computes SHA256, returns metadata, and is used by the CLI; add unit tests for those outcomes.
Written by the indexing model from the issue text.
Description
Summary
The CLI has skill pack which validates a skill directory and creates a .skill ZIP bundle with SHA256. This is currently in packages/cli/src/commands/skills/pack.ts. Promoting it to the SDK enables CI/CD pipelines and platform tooling to build skill bundles without the CLI.
Proposed API
interface PackSkillResult {
success: boolean;
name?: string;
version?: string;
path?: string;
sha256?: string;
size?: number;
error?: string;
}
// On the Mpak facade or as a standalone utility:
async packSkill(skillDir: string, outputPath?: string): Promise<PackSkillResult>
Acceptance Criteria
- Validates skill directory before packing (reuses SDK validation from #75)
- Creates
.skillZIP bundle with correct directory structure - Computes SHA256 hash
- Returns metadata (name, version, path, sha256, size)
- Unit tests
- CLI
skill packupdated to use SDK method
Priority
Lower than #74 and #75 — this is a build-time operation, not runtime. But completes the full skill lifecycle in the SDK.
- 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