discipline

Bulletproof agent operating protocol. 15 failure-prevention rules distilled from 120+ real sessions and 10 agent definitions. Covers fabrication, constraint tracking, verification, scoping, retry discipline, and communication. Load before any task to prevent the most common agent failure modes.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/discipline/SKILL.md

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and exceptionally strong on workflow clarity thanks to explicit checklists, a numbered retry process, and escalation feedback loops, but it is somewhat verbose and monolithic with no progressive disclosure structure for its length.

Suggestions

Trim rhetorical openers and redundant framing across the 15 rules (e.g., drop lines like "The single most dangerous failure mode") to tighten token efficiency.

Consider splitting the rule catalog into a referenced file (e.g., rules.md) with a short overview and Pre-Flight/Post-Flight checklists kept inline in SKILL.md, giving the long body a one-level-deep navigation structure.

Add a one-line table of contents or overview at the top so the 15 rules are scannable before reading the full body.

Dimension	Reasoning	Score
Conciseness	Each rule uses a tight, repeatable "What this looks like / The rule" structure with concrete anti-patterns, but rhetorical openers ("The single most dangerous failure mode. It has caused more blown sessions than any other pattern.") and minor restatement across 15 rules add padding that could be trimmed.	3 / 5
Actionability	Guidance is concrete and executable for an instruction-only skill — "Check logs (journalctl, container logs, error output)", "All temporary files go in /tmp", "Check git status before declaring done" — with specific commands and explicit decision rules, though it stops short of copy-paste-ready artifacts.	4 / 5
Workflow Clarity	Explicit validation checkpoints are present as Pre-Flight and Post-Flight checklists, the retry rule gives a numbered 5-step diagnose-then-retry sequence, and the Session Failure Escalation section provides feedback loops ("stop immediately" on each failure state).	5 / 5
Progressive Disclosure	The body is well-organized into 15 numbered sections plus checklists, but at ~350 lines with no bundle files and no overview-then-reference structure, it is a monolithic single-level document with no progressive disclosure navigation.	3 / 5
	Total	15 / 20 Passed

Description

55%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill is and when to load it, with a concrete rule count and named failure domains, but it leans on internal jargon rather than natural user trigger phrases and names domains instead of executable actions.

Suggestions

Add a natural-language "Use when..." trigger clause naming situations a user would actually describe (e.g., "Use when starting any task, especially involving unfamiliar codebases, third-party tools, or destructive changes").

Replace jargon ("failure-prevention rules", "constraint tracking") with terms users say, such as "avoid hallucinations", "follow your instructions exactly", "verify before reporting done".

Lead with the highest-value concrete actions verbs (e.g., "Verify outputs before declaring done, track user constraints across a session, stop and diagnose instead of retrying blindly") instead of naming abstract domains.

Dimension	Reasoning	Score
Specificity	Lists six concrete behavioral domains ("fabrication, constraint tracking, verification, scoping, retry discipline, and communication") and a concrete rule count ("15 failure-prevention rules"), but these are topic areas rather than verb-driven actions, so coverage is broad yet not action-comprehensive.	3 / 5
Completeness	The "what" is clear (15 rules covering six failure domains) and an equivalent explicit trigger clause exists ("Load before any task to prevent the most common agent failure modes"), though the "when" is a blanket always-load rather than need-based triggers.	4 / 5
Trigger Term Quality	Phrases like "bulletproof agent operating protocol", "failure-prevention rules", and "constraint tracking" are internal jargon; only generic terms ("agent", "task") appear, and the natural phrases a user would actually say when needing this skill are missing.	2 / 5
Distinctiveness Conflict Risk	The agent-operating-protocol niche is mostly distinct from tool-oriented skills, with only minor overlap risk against other behavioral/meta skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: av/harbor
Path: .agents/skills/discipline/SKILL.md
Commit: 67cbe66

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.