.claude/skills/release/SKILL.md
Cut an npm release for the structured-context project. Use when the user asks to cut a release, publish a new version, or run /release <major|minor|patch>.
npx skillsauth add mindsocket/ost-tools releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Cut a $ARGUMENTS release (major, minor, or patch).
Verify the branch is main and working tree is clean. If not, stop and tell the user.
Bump the version — this automatically runs lint, tests, commits, and pushes with tags:
bun pm version $ARGUMENTS
If lint or tests fail, stop and report the errors.
Tell the user to run these commands in their terminal to complete the release (npm requires browser-based authentication that Claude cannot handle):
npm login && npm publish
Once the user confirms publish succeeded, verify it's live by running:
npm view structured-context version
bunx structured-context@latest --version
The first confirms the registry has the new version. The second confirms the published package runs correctly. Report both results to the user.
tools
Use this skill when editing structured markdown content in Obsidian to ensure it conforms to a schema, or when authoring or debugging schemas. Trigger when: (1) content needs validating after edits, (2) schema files or rules need creating or updating, (3) configuring or designing a schema for a space, (4) troubleshooting unexpected validation errors, (5) running structured-context CLI commands.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------