Sovereign Skills for Coding Workflows
A modular skill set for managing coding projects from setup through daily work, review, and governance.
- Source repo
- AlexZio00/sovereign-skills
- Stars
- ★ 146
- Last updated
- 2d ago
- License
- MIT
- Primary language
- Python
- FA score
- 70/100 · Some gaps
At a glance
- How it runs
- Works with
- Portable with changesCodex · Claude Code
- Cost
- Free, no paid service needed
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- A developer maintaining a Claude Code project who wants scope, an editable boundary, and a verifiable completion loop before implementation.
- Not a fit if
- Teams that need skills to run unchanged in any coding agent
- Source review
- 70/100 · Some gaps
What does this agent do, and when should you use it?
Sovereign Skills contains 22 standalone skill directories, each described by a SKILL.md workflow and, where needed, bundled Python helpers. It covers project scaffolding, scope definition, execution discipline, pre-push checks, code review, session handoffs, and audits of documentation and evaluations. Users invoke skills as slash commands in Claude Code, install them under Codex's .agents/skills/ path, or copy the Markdown instructions into Cursor and other agents that read Markdown. Skills read project files and optional session records, run checks or guide an agent through reviews, then produce lists, scores, audit findings, or next-action suggestions. This is a skill collection installed into an agent environment, not a standalone service; some workflows refer to optional agents and document skip behavior or fallback steps when they are absent.
For a new project, /project-init generates CLAUDE.md, ROADMAP, .gitignore, and .env.example from an interview, then /setup configures rules, hooks, memory, routing, and agents. In the daily flow, /scope defines boundaries and exit criteria, /freeze declares the editable zone, and /goal-lock enforces a PLAN→DO→VERIFY loop; /pre-push scans outgoing changes for secrets, runs project build/tests and lint, and performs AI code review. /code-autopsy produces a 12-question review with severity scoring and a deployment verdict, while /session-start and /session-checkpoint read or save handoffs and lessons. Governance skills scan projects, audit loaded documentation, check for circular evaluation, trace duplicate copies of a fact, or inspect skill routing; outputs include gap lists, coverage maps, scores, findings, and recommendations. Skills install as local directories and read project files; no network service or remote API call is documented.
- A developer maintaining a Claude Code project who wants scope, an editable boundary, and a verifiable completion loop before implementation.
- An engineer preparing a push who wants secrets scanning, build/tests, lint, and AI review in one workflow.
- A solo developer working across sessions who needs to restore handoffs, extract lessons, and save state for the next session.
- A maintainer of custom skills who wants usage tracking, snapshots and rollback, or checks for trigger-description collisions.
- An engineer responsible for documentation or evaluation quality who needs to audit context drift, duplicated facts, or evaluation leakage.
How do you install or deploy this agent?
For Claude Code, the simple installation method is to clone the repository and copy the skill directories you want. To copy every directory containing SKILL.md:
git clone https://github.com/AlexZio00/sovereign-skills.git
cd sovereign-skills
for d in */; do [ -f "$d/SKILL.md" ] && cp -r "$d" ~/.claude/skills/; doneTo install one skill, for example:
cp -r goal-lock ~/.claude/skills/Codex user-level skills go under ~/.agents/skills/; repository-level skills go under .agents/skills/:
cp -r goal-lock ~/.agents/skills/goal-lock/The repository also documents a Claude Code marketplace route. For Cursor and other agents, copy SKILL.md into the agent's instruction path. Skills with bundled scripts require Python 3.9+; pre-push includes a Perl fallback for secret scanning. No API key is listed as required.
How do you use this agent?
In Claude Code, invoke a skill by typing its slash command, for example:
/project-checkA new-project sequence can start with:
/project-init
/setup
/session-startCodex discovers skills under .agents/skills/<skill-name>/SKILL.md; user-level skills can be placed at ~/.agents/skills/<skill-name>/. For another agent that reads Markdown instructions, place SKILL.md in its instruction path and use that agent's supported invocation method. Individual skills read project files; session skills read or write handoff, lesson, and state records when those shared files are present.
What are this agent's strengths and limitations?
- The 22 skills span setup, scope control, review, session management, and governance, and can be installed individually or used as a lifecycle sequence.
pre-pushchecks staged and outgoing changes and combines secret scanning, build/tests, lint, and AI review.- The documentation names the Python 3.9+ script requirement and describes optional agents and their fallbacks, making dependencies easier to assess.
- It documents direct installation for Claude Code and Codex, plus a Markdown-copy path for Cursor and other agents.
- Claude Code uses slash commands, while Codex and other agents require installation in their own paths; invocation is not identical across platforms.
- Some script-backed skills need Python 3.9+; Perl is documented only as a secret-scanning fallback for
pre-push. - Some review steps depend on optional agents that are not included in the repository; missing agents may cause steps to be skipped or replaced by a fallback.
- The documentation does not quantify model-call costs, time saved, or review accuracy.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Sovereign Skills for Coding Workflows This agent | 70 · Some gaps | Agent plugin / skillFree | ★ 146 | 2d ago | Python | Codex · Claude Code |
| GStack Engineering Workflow | 80 · Good | Agent plugin / skillFree + model costs | ★ 137k | today | TypeScript | Claude Code |
| Finding-Unknowns Skills | 76 · Good | Agent plugin / skillFree | ★ 353 | 25d ago | Python | Claude Code · Claude.ai |
| Itqan Engineering | 80 · Good | Agent plugin / skillFree + model costs | ★ 12 | 24d ago | Shell | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
The material says several skills are read-only or make recommendations, ssot-audit consolidates duplicates only after approval, clean-room uses an isolated subagent, and pre-push scans for secrets and blocks on high-severity findings. This supports some least-privilege, confirmation, and side-effect controls. Session skills’ read/write files and optional dependencies are described, but there is no concrete sensitive-data handling policy or evidence of dependency pinning or vulnerability management, so full marks are not justified. MIT licensing and contribution guidance establish attribution, while publisher identity remains unknown as specified.
The README describes the helper scripts’ Python version, invocation from different install locations, and fallback or stop behavior when optional dependencies are missing; it also outlines deterministic workflows for several skills. This supports ordinary usability. Deductions reflect that the supplied material lacks the individual skill contents, script implementations, and independent verification, so the README’s overview cannot establish consistency across all skills or detailed failure messages.
The material organizes skills around new projects, existing projects, daily work, governance audits, and skill authors, and lists Claude Code, Codex, and Cursor support plus fallbacks for missing optional agents. Audience and scenario coverage is strong. Deductions reflect that cross-tool adaptation relies largely on generic Markdown and manual path substitution, with limited evidence about Codex/Cursor specifics and trigger boundaries.
The README provides phase-based navigation, a skill catalog, lifecycle diagram, installation steps, requirements, optional-dependency notes, and a file-conventions link. The license is explicit, version v6.5.15 is stated with a link to the full changelog, and contributions are invited. Deductions reflect that the supplied material omits the changelog itself and a clear maintenance commitment; FAQ and limitations are scattered, and long-term naming stability cannot be established.
The skills claim to produce directly useful artifacts such as scope specifications, audit lists, prioritized fix lists, session handoffs, and push reviews, with standalone installation options. These outputs appear useful for coding-agent workflows. Deductions reflect the configuration and coordination cost of a 22-skill collection and the absence of usage data or outcome comparisons in the supplied material.
The README gives a concrete version, skill and script names, trigger commands, counts for some scanning patterns, and a change summary, making some claims traceable. It also associates design claims with skill descriptions. Deductions reflect that the supplied source consists only of the README, license, and workflow configuration; it lacks skill bodies, scripts, changelog contents, and execution results to corroborate many functional claims. This review does not claim execution or independent testing.
- Functional, scan-coverage, and fallback claims in the README could not be cross-checked against the skill bodies or scripts in the supplied material.
- Some installed skills read or write session handoffs, memory, lessons, and invocation logs; confirm those paths and contents fit your data-handling requirements before deployment.
FAQ
Do I have to use Claude Code?
.agents/skills/; for Cursor and other agents that read Markdown, copy SKILL.md into the agent's instruction path.Do I need an API key?
pre-push includes AI code review, but the model or service costs are not specified.Do I need Python to install the skills?
scripts/*.py helpers require Python 3.9+ to run those scripts. The documentation says each skill specifies whether to use a manual fallback or stop if its script cannot run.What happens if optional review agents are missing?
pre-push can use an inline fast review and mark agent steps skipped; other skills describe using a general-purpose subagent prompt or skipping the relevant report step.Do the skills automatically change the whole project?
/next-action only proposes actions and eval-leakage-audit is read-only; /ssot-audit identifies repeated facts and their source, then consolidates copies only after approval.