my_agent_skill

Personal agent skills packaged for Claude Code, Codex, and related agent clients.

Skills CLI

This repo can be published as a lowercase scoped npm package, for example opsx-agent-skills. npm package names cannot contain uppercase letters, so @Ethan_Zhang/skills is not valid.

One-Time Update

npx -y opsx-agent-skills@latest update

By default, update syncs package-managed skills to ~/.claude/skills. Other useful forms:

npx -y opsx-agent-skills@latest update --client codex
npx -y opsx-agent-skills@latest update --client all
npx -y opsx-agent-skills@latest update --dry-run
npx -y opsx-agent-skills@latest update --target /tmp/test-skills
npx -y opsx-agent-skills@latest list

The updater writes .skills-lock.json in each target skill root and only rewrites skills managed by this package. If a destination skill directory exists but is not recorded in the lock file, the updater reports a conflict and leaves that directory untouched.

Claude SessionStart Hook

Add this to user-level ~/.claude/settings.json to refresh before each Claude Code session:

{
  "hooks": {
    "SessionStart": [
      {
        "matcher": "*",
        "hooks": [
          {
            "type": "command",
            "command": "npx -y opsx-agent-skills@latest update --client claude >/dev/null 2>&1 || true",
            "timeout": 60
          }
        ]
      }
    ]
  }
}

Codex Refresh

Codex can use the same CLI:

npx -y opsx-agent-skills@latest update --client codex

For a guaranteed refresh before Codex starts, use a shell wrapper or alias:

alias codex='npx -y opsx-agent-skills@latest update --client codex >/dev/null 2>&1 || true; command codex'

Session-start hooks may update files after the current session has already loaded its skill list, so hook-based updates are safest when you only need the next session to see new skills.

Local Validation And Publish

npm install
npm run test:local
npm run pack:check
npm pack

To publish publicly:

npm login
npm publish --access public

This repo includes .github/workflows/publish.yml for automated publishing with npm Trusted Publishing. To enable it:

1. Push this repository to GitHub.
2. On npmjs.com, open the package settings for opsx-agent-skills.
3. Add a Trusted Publisher:
   • Provider: GitHub Actions
   • Organization or user: EthenZhang
   • Repository: my_agent_skill
   • Workflow filename: publish.yml
4. Push a semver tag:

npm version patch
git push --follow-tags

The workflow runs validation and publishes to npm when tags matching v*.*.* are pushed. It can also be started manually from the GitHub Actions tab. Trusted Publishing uses GitHub OIDC, so no long-lived NPM_TOKEN secret is required.

OpenSpec OPSX Usage

Codex App can invoke the global custom prompts directly:

• /prompts:opsx-explore
• /prompts:opsx-propose
• /prompts:opsx-apply
• /prompts:opsx-archive

Codex CLI currently does not dispatch these custom prompt commands through the interactive slash-command parser. In CLI sessions, use the OpenSpec skills with plain text instead:

• opsx explore <topic>
• opsx propose <change or request>
• opsx apply <change>
• opsx archive <change>

If you specifically want to type the Claude-style alias in Codex CLI, prefix it with one leading space so the CLI sends it as normal text instead of trying to parse it as a built-in slash command:

• /opsx:explore <topic>
• /opsx:propose <change or request>
• /opsx:apply <change>
• /opsx:archive <change>

The leading space is intentional. Without it, Codex CLI treats /opsx:explore as an unknown slash command before the model or skill loader can see it.