Add packSkill() to SDK for building .skill bundles programmatically

Open
#76 0 comments 0 reactions 0 assignees View on GitHub

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

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

pkg/sdk-typescript

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 .skill ZIP bundle with correct directory structure
  • Computes SHA256 hash
  • Returns metadata (name, version, path, sha256, size)
  • Unit tests
  • CLI skill pack updated 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NimbleBrainInc/mpak

All issues in NimbleBrainInc/mpak

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.