Skip to content

Publish optional CLI to npm or attach release artifact #2

Description

@syf2211

The Skill already installs from GitHub/skills.sh. The optional CLI and hooks still require clone + npm install + build.\n\nThis issue tracks the next distribution step:\n\n- Decide npm package name and release process.\n- Keep postinstall opt-in only; no silent user config writes.\n- Make README and Hook docs point to the published CLI only after it exists.\n- Add release verification for install + setup + session-end fallback.\n\nThis is not required for basic Skill usage, but it reduces friction for users who want reports and hooks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions