Company Radar
Varnan-Tech/opendirectory
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
Install Openclaw GitHub Repo Commander
$ npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills openclaw-github-repo-commander --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/openclaw-github-repo-commander .claude/skills/openclaw-github-repo-commander && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openclaw-github-repo-commander" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/openclaw-github-repo-commander into .claude/skills/openclaw-github-repo-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-github-repo-commander", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/openclaw-github-repo-commanderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills openclaw-github-repo-commander --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/openclaw-github-repo-commander .agents/skills/openclaw-github-repo-commander && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openclaw-github-repo-commander" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/openclaw-github-repo-commander into .agents/skills/openclaw-github-repo-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-github-repo-commander", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills openclaw-github-repo-commander --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/openclaw-github-repo-commander .cursor/skills/openclaw-github-repo-commander && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openclaw-github-repo-commander" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/openclaw-github-repo-commander into .cursor/skills/openclaw-github-repo-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-github-repo-commander", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/openclaw-github-repo-commander--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills openclaw-github-repo-commander --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/openclaw-github-repo-commander .gemini/skills/openclaw-github-repo-commander && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openclaw-github-repo-commander" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/openclaw-github-repo-commander into .gemini/skills/openclaw-github-repo-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-github-repo-commander", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills openclaw-github-repo-commanderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/openclaw-github-repo-commander .github/skills/openclaw-github-repo-commander && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openclaw-github-repo-commander" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/openclaw-github-repo-commander into .github/skills/openclaw-github-repo-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-github-repo-commander", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills openclaw-github-repo-commander --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/openclaw-github-repo-commander .opencode/skills/openclaw-github-repo-commander && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openclaw-github-repo-commander" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/openclaw-github-repo-commander into .opencode/skills/openclaw-github-repo-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-github-repo-commander", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openclaw-github-repo-commander- GitHub stars
- 47k
- Used in
- 2 other repos
- Token cost
- ~1k tokens
- SKILL.md length
- 441 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 1,354
- Repo updated
- First seen
- Licence
- MIT
At a glance
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
- Works in 7 steps: Intake → Execution → Reflection → …
- Tasks that involve Competitor analysis
- SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 4 more sections
- Runs Shell scripts from its folder; reaches github.com
What it does
Openclaw GitHub Repo Commander is an agent skill from sickn33/agentic-awesome-skills. 7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/repo-audit.sh`).
It sits in Marketing & SEO, covering Competitor analysis and Pull requests. It works with GitHub. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Competitor analysis
- Tasks that involve Pull requests
Example prompts
- “/openclaw-github-repo-commander”
Requirements
- A Bash shell
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Openclaw GitHub Repo Commander loads about 1k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 441 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:83
- ❌ Don't commit `node_modules/` or `.env` files
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 441 words, ~1,013 tokens.
Download SKILL.mdSave it as
.claude/skills/openclaw-github-repo-commander/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- openclaw-github-repo-commander
- description
- 7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
- category
- development-and-testing
- risk
- safe
- source
- community
- date_added
- 2026-03-18
- author
- wd041216-bit
- tags
- github, git, repository, audit, cleanup, workflow, devtools, automation, code-review, security
- tools
- claude, cursor
OpenClaw GitHub Repo Commander
Overview
A structured 7-stage super workflow for comprehensive GitHub repository management. This skill automates repository auditing, cleanup, competitor benchmarking, and optimization — turning a messy repo into a clean, well-documented, production-ready project.
When to Use This Skill
- Use when you need to audit a repository for secrets, junk files, or low-quality content
- Use when the user says "clean up my repo", "optimize my GitHub project", or "audit this library"
- Use when reviewing or creating pull requests with structured analysis
- Use when comparing your project against competitors on GitHub
- Use when running
/super-workflowor/openclaw-github-repo-commanderon a repo URL
How It Works
Stage 1: Intake
Clone the target repository, define success criteria, and establish baseline metrics.
Stage 2: Execution
Run scripts/repo-audit.sh <repo-path> from this skill directory — automated read-only checks for:
- Hardcoded secrets (
ghp_,sk-,AKIA, etc.) - Tracked
node_modules/or build artifacts - Empty directories
- Large files (>1MB)
- Missing
.gitignorecoverage - Broken internal README links
Stage 3: Reflection
Deep manual review beyond automation: content quality, documentation consistency, structural issues, version mismatches.
Stage 4: Competitor Analysis
Search GitHub for similar repositories. Compare documentation standards, feature coverage, star counts, and community adoption.
Stage 5: Synthesis
Consolidate all findings into a prioritized action plan (P0 critical / P1 important / P2 nice-to-have).
Stage 6: Iteration
Execute the plan: delete low-value files, fix security issues, upgrade documentation, add CI workflows, update changelogs.
Stage 7: Validation
Re-run the audit script (target: 7/7 PASS), verify all changes, push to GitHub, and deliver a full report.
Examples
Example 1: Full Repo Audit
/openclaw-github-repo-commander https://github.com/owner/my-repoRuns all 7 stages and produces a detailed before/after report.
Show full SKILL.md (178 more words)Show less
Example 2: Quick Cleanup
Clean up my GitHub repo — remove junk files, fix secrets, add .gitignoreExample 3: Competitor Benchmarking
Compare my skill repo with the top 5 similar repos on GitHubBest Practices
- ✅ Always run Stage 7 validation before pushing
- ✅ Use semantic commit messages:
chore:,fix:,docs: - ✅ Check the
pr_todo.jsonfile for pending reviewer requests - ❌ Don't skip Stage 4 — competitor analysis reveals blind spots
- ❌ Don't commit
node_modules/or.envfiles
Security & Safety Notes
- The audit script scans for common secret patterns but excludes
.github/workflows/to avoid false positives - The bundled script is read-only: it reports findings and never deletes, rewrites, stages, commits, or pushes files
- All
ghCLI operations use the user's existing authentication — no credentials are stored by this skill - The skill never modifies files without explicit user confirmation in Stage 6
Source Attribution
Originally contributed by @wd041216-bit in PR #340. No standalone upstream repository is currently available for this skill.
License: MIT | Version: 4.0.0
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in skills/openclaw-github-repo-commander of sickn33/agentic-awesome-skills.
- SKILL.md
- scripts/repo-audit.sh
Open the folder on GitHubat commit ec02547
Used in 2 other repositories
We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/openclaw-github-repo-commanderantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/openclaw-github-repo-commander+1 more
- henryalouf/ruflow.agents/skills/openclaw-github-repo-commander.agents/skills/antigravity-awesome-skills/skills/openclaw-github-repo-commander+4 more
Compare with similar skills
Openclaw GitHub Repo Commander next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openclaw GitHub Repo Commander this skillsickn33/agentic-awesome-skills | 47k | 2 repos | ~1k | Automated safety check: Notes | MIT | |
| Company RadarVarnan-Tech/opendirectory | 674 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw | 23k | — | ~693 | Automated safety check: Pass | Apache-2.0 | |
| GitHubkostja94/marketing-skills | 1k | — | ~4.5k | Automated safety check: Pass | MIT | |
| GitHub Readmethatrebeccarae/claude-marketing | 162 | — | ~2.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Nemoclaw Maintainer Normalize Title Tags
NVIDIA/NemoClaw
Remove bracketed NemoClaw tags from GitHub issue and PR titles.
GitHub
kostja94/marketing-skills
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists.
GitHub Readme
thatrebeccarae/claude-marketing
Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
More from sickn33/agentic-awesome-skills
All 1,354 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Content Creator
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
Related
Works with
Categories
Questions about Openclaw GitHub Repo Commander
What does Openclaw GitHub Repo Commander do?
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis. Openclaw GitHub Repo Commander is an agent skill from sickn33/agentic-awesome-skills.
When should I use Openclaw GitHub Repo Commander?
Openclaw GitHub Repo Commander fits situations like: tasks that involve Competitor analysis; tasks that involve Pull requests.
How do I install Openclaw GitHub Repo Commander in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a claude-code`. Or copy the skill folder (skills/openclaw-github-repo-commander in sickn33/agentic-awesome-skills) into .claude/skills/openclaw-github-repo-commander in your project. Claude Code loads it when a task matches its description.
How do I install Openclaw GitHub Repo Commander in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a codex`. Or copy the skill folder (skills/openclaw-github-repo-commander in sickn33/agentic-awesome-skills) into .agents/skills/openclaw-github-repo-commander in your project. Codex loads it when a task matches its description.
Can I use Openclaw GitHub Repo Commander in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill openclaw-github-repo-commander -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-github-repo-commander, .gemini/skills/openclaw-github-repo-commander, .github/skills/openclaw-github-repo-commander and .opencode/skills/openclaw-github-repo-commander in your project.
What does Openclaw GitHub Repo Commander need to run?
Going by SKILL.md and its folder, Openclaw GitHub Repo Commander needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Openclaw GitHub Repo Commander access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Openclaw GitHub Repo Commander safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Openclaw GitHub Repo Commander use?
Openclaw GitHub Repo Commander is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openclaw GitHub Repo Commander use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Openclaw GitHub Repo Commander?
Skills that share tags, products or a category with Openclaw GitHub Repo Commander: Company Radar (Varnan-Tech/opendirectory, 674 stars), Nemoclaw Maintainer Normalize Title Tags (NVIDIA/NemoClaw, 23k stars), GitHub (kostja94/marketing-skills, 1k stars) and GitHub Readme (thatrebeccarae/claude-marketing, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openclaw GitHub Repo Commander?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.