SpecterOps / SpecterOps/og-docs-automation

Suggestion: Use skills npm package instead of Install-CodexSkill.ps1

Open Beginner friendly
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
5
Forks
1
PR merge metrics
No merged PRs in 30d

Description

I would personally drop Install-CodexSkill.ps1 in favor of running

npx skills add SpecterOps/og-docs-automation --skill * --agent codex claude-code --project --yes

OR

npx skills add ./docs/og-docs-automation/skills --skill * --agent codex claude-code --project --yes

It produces really nice output:

███████╗██╗  ██╗██╗██╗     ██╗     ███████╗
██╔════╝██║ ██╔╝██║██║     ██║     ██╔════╝
███████╗█████╔╝ ██║██║     ██║     ███████╗
╚════██║██╔═██╗ ██║██║     ██║     ╚════██║
███████║██║  ██╗██║███████╗███████╗███████║
╚══════╝╚═╝  ╚═╝╚═╝╚══════╝╚══════╝╚══════╝

┌   skills 
│
◇  Source: https://github.com/SpecterOps/og-docs-automation.git
│
◇  Repository cloned
│
◇  Found 2 skills
│
●  Installing all 2 skills

│
◇  Installation Summary ────────────────────────────────────────────────────────────╮
│                                                                                   │
│  ~\source\repos\SpecterOps\openhound-okta\.agents\skills\openhound-edge-docs      │
│    universal: Codex                                                               │
│    symlink → Claude Code                                                          │
│    overwrites: Codex, Claude Code                                                 │
│                                                                                   │
│  ~\source\repos\SpecterOps\openhound-okta\.agents\skills\openhound-entity-panels  │
│    universal: Codex                                                               │
│    symlink → Claude Code                                                          │
│    overwrites: Codex, Claude Code                                                 │
│                                                                                   │
├───────────────────────────────────────────────────────────────────────────────────╯
│
◇  Security Risk Assessments ─────────────────────────────────────────────╮
│                                                                         │
│                           Gen               Socket            Snyk      │
│  openhound-edge-docs      Safe              0 alerts          Low Risk  │
│  openhound-entity-panels  Safe              0 alerts          Low Risk  │
│                                                                         │
│  Details: https://skills.sh/SpecterOps/og-docs-automation               │
│                                                                         │
├─────────────────────────────────────────────────────────────────────────╯
│
◇  Installation complete

│
◇  Installed 2 skills ────────────────────────────────────────────────────────────────╮
│                                                                                     │
│  ✓ ~\source\repos\SpecterOps\openhound-okta\.agents\skills\openhound-edge-docs      │
│    universal: Codex                                                                 │
│    symlinked: Claude Code                                                           │
│  ✓ ~\source\repos\SpecterOps\openhound-okta\.agents\skills\openhound-entity-panels  │
│    universal: Codex                                                                 │
│    symlinked: Claude Code                                                           │
│                                                                                     │
├─────────────────────────────────────────────────────────────────────────────────────╯
│
└  Done!  Review skills before use; they run with full agent permissions.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by locating Install-CodexSkill.ps1 and any documentation or setup references to it. Compare those instructions with the provided npx skills add commands; done means the old installation path is replaced by the skills package approach and the documented commands work for the repository's skills.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, powershell
Domain
developer-experience, tooling
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.