laststance-publish-skill

name	laststance-publish-skill
description	Publish skill to registry

Publish Skill to laststance/skills

Codex Compatibility

When running this skill in Codex, translate Claude Code-only primitives before acting: AskUserQuestion -> chat/request_user_input, TodoWrite -> update_plan, Task/TaskCreate/TeamCreate/SendMessage -> spawn_agent/send_input/wait_agent when available and allowed, and EnterPlanMode/ExitPlanMode -> a concise chat plan plus explicit approval. Resolve Read/Write/Edit/Bash/WebSearch/WebFetch to Codex file/shell/web tools, and map ~/.claude/... paths to ~/.agents/... or ~/.codex/... unless the task explicitly targets Claude Code.

Cursor Compatibility

When running this skill in Cursor Agent, translate Claude Code-only primitives before acting: AskUserQuestion -> AskQuestion; TodoWrite -> Cursor TodoWrite or an equivalent checklist; Task/TaskCreate/TeamCreate/SendMessage/multi-agent flows -> Cursor Task (subagents), parallel Tasks, or run_in_background when allowed (TeamCreate/SendMessage may have no exact match); EnterPlanMode/ExitPlanMode -> Plan mode (SwitchMode / CreatePlan) plus explicit user approval. Resolve Read/Write/Edit/StrReplace/Bash/web/search/MCP via Cursor Composer or Agent equivalents. MCP names written as mcp__server__tool typically map to call_mcp_tool with configured server identifiers. Map ~/.claude/... to ~/.cursor/skills/, .cursor/skills/, and .cursor/rules/ unless the task explicitly targets Claude Code.

Publish a tested skill to the laststance/skills repository for distribution via npx skills add.

Prerequisites

• Skill is stable (passed Phase 2 testing in ~/.codex/skills/ and ~/.vscode/skills/)
• Repository cloned at ~/laststance/skills
• Skill has a valid SKILL.md with frontmatter (name, description)

Publish Steps

1. Copy skill to repository

mkdir -p ~/laststance/skills/skills/<name>
cp -r ~/.claude/skills/<name>/* ~/laststance/skills/skills/<name>/

Only copy files needed for the skill (SKILL.md + supporting files). Do NOT copy test artifacts or local-only files.

2. Update README.md (4 places)

Sections A–C maintain alphabetical order; D is a count.

A. Install commands — Add to the specific skill install list:

npx skills add laststance/skills --skill <name>

B. Available Skills table — Add row in alphabetical position:

| [<name>](skills/<name>/) | <description> | <dependencies or —> |

Dependencies format:

• No deps: —
• Optional: [Name](url) (recommended)
• Required: [Name](url) **(required)**

C. Usage examples — Add entry in alphabetical position:

/<name> <typical-args>              # Short description

D. Skills count badge — bump the skill count in the shields.io badge near the top of the README:

img.shields.io/badge/skills-<N>-2563EB

<N> = total skill count after this publish: ls ~/laststance/skills/skills/*/SKILL.md | wc -l.

3. Commit and push

cd ~/laststance/skills
git add skills/<name>/ README.md
git commit -m "$(cat <<'EOF'
feat: add <name> skill — <short description>
EOF
)"
git push

Checklist

• Skill directory copied to ~/laststance/skills/skills/<name>/
• README install command added (alphabetical)
• README skills table row added (alphabetical)
• README usage example added (alphabetical)
• README skills count badge bumped (skills-<N>)
• Committed with feat: add <name> skill format
• Pushed to remote

After Publish (CLI Install)

Once merged, install via CLI to create symlinks across all AI tools:

npx skills add laststance/skills
# or specific skill:
npx skills add laststance/skills --skill <name>

This installs to ~/.agents/skills/<name>/ and creates symlinks in ~/.claude/skills/, ~/.codex/skills/, ~/.vscode/skills/, etc. The hand-created original in ~/.claude/skills/ is replaced by the symlink.