Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Run focused verification for a ticket and report what it actually covers.
Install Verify Discipline
$ npx skills add Eigenwise/eigenwise-toolshed --skill verify-discipline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed verify-discipline --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/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/sidequest/skills/verify-discipline .claude/skills/verify-discipline && 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 "verify-discipline" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/verify-discipline into .claude/skills/verify-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-discipline", 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/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/verify-disciplineType 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 Eigenwise/eigenwise-toolshed --skill verify-discipline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed verify-discipline --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/sidequest/skills/verify-discipline .agents/skills/verify-discipline && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-discipline" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/verify-discipline into .agents/skills/verify-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-discipline", 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 Eigenwise/eigenwise-toolshed --skill verify-discipline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed verify-discipline --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/sidequest/skills/verify-discipline .cursor/skills/verify-discipline && 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 "verify-discipline" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/verify-discipline into .cursor/skills/verify-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-discipline", 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/Eigenwise/eigenwise-toolshed.git --path plugins/sidequest/skills/verify-discipline--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 Eigenwise/eigenwise-toolshed --skill verify-discipline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed verify-discipline --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/sidequest/skills/verify-discipline .gemini/skills/verify-discipline && 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 "verify-discipline" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/verify-discipline into .gemini/skills/verify-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-discipline", 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 Eigenwise/eigenwise-toolshed verify-disciplineInstalls 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 Eigenwise/eigenwise-toolshed --skill verify-discipline -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/sidequest/skills/verify-discipline .github/skills/verify-discipline && 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 "verify-discipline" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/verify-discipline into .github/skills/verify-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-discipline", 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 Eigenwise/eigenwise-toolshed --skill verify-discipline -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed verify-discipline --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/sidequest/skills/verify-discipline .opencode/skills/verify-discipline && 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 "verify-discipline" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/verify-discipline into .opencode/skills/verify-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-discipline", 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
verify-discipline- GitHub stars
- 277
- Token cost
- ~964 tokens
- SKILL.md length
- 517 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run focused verification for a ticket and report what it actually covers.
- Works in 4 steps: Find the project's real commands in its… → Pick the closest consumer, regression… → Run that focused check while editing. A… → …
- Verifying a change
- SKILL.md covers Focused checks for executors, Measured quality without… and Keep the result readable
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Verify Discipline is an agent skill from Eigenwise/eigenwise-toolshed. Run focused verification for a ticket and report what it actually covers. The orchestrator runs the one combined full gate after integration. Use when running tests, verifying a change, or choosing a test command.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. The repository describes itself as: Six Claude Code plugins for the work that keeps coming back: repo maps, conditional rules, ticketed parallel work, extra subscription models, local usage metrics, and guided setup. The licence is MIT.
When your agent uses it
- Verifying a change
- Choosing a test command
Example prompts
- “/verify-discipline”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Find the project's real commands in its documented scripts. Do not guess flags.
- Pick the closest consumer, regression input, or test that can fail for the behavior you changed.
- Run that focused check while editing. A nontrivial behavior change needs the smallest meaningful
- Commit the final scoped candidate, then run the ticket's exact verifier once for the final
What it can do on your machine
Read from SKILL.md and the folder at commit 92c16cd. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Verify Discipline loads about 964 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 517 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 passed
The automated check found no risky patterns in SKILL.md.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from Eigenwise/eigenwise-toolshed at commit 92c16cd, republished under its MIT licence (© Eigenwise). 517 words, ~964 tokens.
Download SKILL.mdSave it as
.claude/skills/verify-discipline/SKILL.md (or your agent's skills folder).- name
- verify-discipline
- description
- Run focused verification for a ticket and report what it actually covers. The orchestrator runs the one combined full gate after integration. Use when running tests, verifying a change, or choosing a test command.
Verify discipline
Focused checks for executors
- Find the project's real commands in its documented scripts. Do not guess flags.
- Pick the closest consumer, regression input, or test that can fail for the behavior you changed.
- Run that focused check while editing. A nontrivial behavior change needs the smallest meaningful runnable regression, not an invented test count.
- Commit the final scoped candidate, then run the ticket's exact verifier once for the final clean-candidate capture and report the behavior and assertion or consumer it exercised. A changed candidate needs fresh verification. Do not claim broader coverage ran when it did not.
The orchestrator delivers the wave through the real pinned delivery verifier, then runs one combined full gate after integration and before versioning. Re-gate a changed tree after rebase. Reuse assembled-tree proof only under the runtime's exact tree, command, candidate, and capture authority checks. An executor does not run or schedule a broad suite unless the ticket's contract specifically requires it. A safety-sensitive contract can require independent review for a contract-named seam the oracle cannot exercise or a required high-stakes review. Multiple lenses need distinct named risks.
Measured quality without duplicate suites
Run the project's configured quality gate when the briefing names one and report its per-function rows
honestly: unmeasured bodies stay unmeasured, no averages. Use the existing local quality owner. Where supported, run an early measured complexity scan before
expensive final coverage. Reuse fresh candidate-verifier coverage for the same checked bytes only when
the actual runner supports it. For a configured gate, missing analyzer or coverage stays UNVERIFIED. Never substitute tracked
Lizard/proportional attribution, pin quality:crap as authority, or rerun a full suite merely for
already captured compatible coverage. Tooling and reports stay local and uncommitted; untouched legacy functions are outside scope.
When none is configured, run the pinned verifier, state once "no quality gate is configured for this
project; Quartermaster setup can add one", and continue. Absence alone never holds, parks or marks work
UNVERIFIED. User rules injected by the host still apply.
Show full SKILL.md (181 more words)Show less
Before a long run, freeze its inputs and validate source, coverage and executed/source-map byte identity. Check native baseline/candidate ownership, clean-state prerequisites, finite deadline and actual resource fit first. Focused real coverage may run separately from the normal final gate when the local owner supports it. Keep source fixed throughout an immutable capture; changed inputs need a fresh run. Report failed checks or missing support honestly, never fabricate passing receipts or weaken standards. Consume the quality owner's evidence; Quartermaster remains setup-only. Reuse genuine compatible execution evidence at final review without a duplicate suite merely for reviewer identity.
Heavy commands follow the parent-named shared-resource handoff in ../sidequest/references/orchestration.md. Without the slot,
continue independent reading/editing/commits, record readiness, and end the turn retaining the claim.
Keep the result readable
The exit code is the verdict. Redirect long commands to a log and show the status and failures; read only the relevant log range on failure. Preserve the command's exit code when filtering output.
If no focused form exists, use the smallest documented check that covers the change. Do not make a full suite an edit loop.
© Eigenwise, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/sidequest/skills/verify-discipline of Eigenwise/eigenwise-toolshed.
Open the folder on GitHubat commit 92c16cd
Compare with similar skills
Verify Discipline 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 |
|---|---|---|---|---|---|---|
| Verify Discipline this skillEigenwise/eigenwise-toolshed | 277 | — | ~964 | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 35k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 9 repos | ~4.3k | Automated safety check: Pass | None | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
More from Eigenwise/eigenwise-toolshed
All 14 skills in this repoAdd Rule
Eigenwise/eigenwise-toolshed
Create or edit a live-rules instruction in the project's atomic rule set.
Map Codebase
Eigenwise/eigenwise-toolshed
Create a self-maintaining codebase map in .claude/.codebase-info/.
Setup
Eigenwise/eigenwise-toolshed
Set up a Claude Code workspace for a new or existing project, informed by hindsight from the user's whole session history.
Groom
Eigenwise/eigenwise-toolshed
Audit a Sidequest board for completed, stale, duplicate, or superseded tickets, then safely close clear cases.
Manage Rules
Eigenwise/eigenwise-toolshed
Inspect, audit, enable, or disable project live-rules. An agent skill from Eigenwise/eigenwise-toolshed.
Toolshed Doctor
Eigenwise/eigenwise-toolshed
Run a read-only health check for Quartermaster and installed Toolshed plugins.
Related
Categories
Questions about Verify Discipline
What does Verify Discipline do?
Run focused verification for a ticket and report what it actually covers. Verify Discipline is an agent skill from Eigenwise/eigenwise-toolshed. Run focused verification for a ticket and report what it actually covers.
When should I use Verify Discipline?
Verify Discipline fits situations like: verifying a change; choosing a test command.
How do I install Verify Discipline in Claude Code?
Run `npx skills add Eigenwise/eigenwise-toolshed --skill verify-discipline -a claude-code`. Or copy the skill folder (plugins/sidequest/skills/verify-discipline in Eigenwise/eigenwise-toolshed) into .claude/skills/verify-discipline in your project. Claude Code loads it when a task matches its description.
How do I install Verify Discipline in Codex?
Run `npx skills add Eigenwise/eigenwise-toolshed --skill verify-discipline -a codex`. Or copy the skill folder (plugins/sidequest/skills/verify-discipline in Eigenwise/eigenwise-toolshed) into .agents/skills/verify-discipline in your project. Codex loads it when a task matches its description.
Can I use Verify Discipline 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 Eigenwise/eigenwise-toolshed --skill verify-discipline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-discipline, .gemini/skills/verify-discipline, .github/skills/verify-discipline and .opencode/skills/verify-discipline in your project.
What does Verify Discipline need to run?
SKILL.md names no scripts, command-line tools or credentials: Verify Discipline is instructions for the agent only.
Does Verify Discipline access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verify Discipline safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verify Discipline use?
Verify Discipline 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 Verify Discipline use?
About 964 tokens (SKILL.md is roughly 3.9k 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 Verify Discipline?
Skills that share tags, products or a category with Verify Discipline: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Discipline?
Eigenwise (a GitHub user) maintains it in Eigenwise/eigenwise-toolshed, which has 277 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: Eigenwise/eigenwise-toolshed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.