Jamie-BitFlight/claude_skills/.claude/skills/boil/SKILL.md
boil
Activates Standard of Excellence enforcement for the current session. Load before starting any task to apply completion standards: finish the whole thing, fix the root cause, ship the complete working result. Blocks partial solutions, workarounds, deferred threads, and invented content limits when the permanent solve is within reach. Triggers: 'do the whole thing', 'boil the ocean', 'standard of excellence', 'finish it completely', before starting any implementation, refactoring, or multi-step t
- Source repository stars
- 64
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-25
- Source checked
- 2026-08-25
Decision brief
What it does: where it fits
Outcome: A task is complete only when all output is delivered (no prohibited exits taken, no workarounds), the Dangling Thread Checklist has no open items, and no PENDING threads remain.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/Jamie-BitFlight/claude_skills --skill ".claude/skills/boil"Inspect the Agent Skill "boil" from https://github.com/Jamie-BitFlight/claude_skills/blob/b70ba8737e664d9e2482912e3ddbe7ecb77e0539/.claude/skills/boil/SKILL.md at commit b70ba8737e664d9e2482912e3ddbe7ecb77e0539. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Workflow
Review the “Workflow” section in the pinned source before continuing.
Review and apply the “Workflow” source section. - 02
Preparation
Before applying any task, inspect the input:
Read the [task-description] argument if provided.Identify whether prior partial work exists — check for TODO, FIXME, or PENDING markers in affected files.Confirm the task scope is understood: what files, what behavior, what "complete" looks like. - 03
The Standard
The marginal cost of completeness is near zero. Complete the whole thing.
Search before building. Check whether the solution already exists before implementing.Test before shipping. Verify observable behavior, not just syntax correctness.Ship the complete thing. The answer is the finished product, not a plan to build it. - 04
Prohibited Exits
NEVER use the following exits when the permanent solve is reachable:
NEVER use the following exits when the permanent solve is reachable: - 05
The One Legitimate Exit — BLOCKED Declaration
When the permanent solve is genuinely unreachable due to an external constraint, use this form. Copy ./assets/blocked-declaration-template.md verbatim into your response and fill in every field. Full contract: ./references/blocked-declaration-contract.md
When the permanent solve is genuinely unreachable due to an external constraint, use this form. Copy ./assets/blocked-declaration-template.md verbatim into your response and fill in every field. Full contract: ./referen…
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 91/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 64 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- Jamie-BitFlight/claude_skills
- Skill path
- .claude/skills/boil/SKILL.md
- Commit
- b70ba8737e664d9e2482912e3ddbe7ecb77e0539
- License
- MIT
- Collected
- 2026-08-25
- Default branch
- main
View the original SKILL.md
Standard of Excellence — Boil the Ocean
Outcome: A task is complete only when all output is delivered (no prohibited exits taken, no workarounds), the Dangling Thread Checklist has no open items, and no PENDING threads remain.
Full source extracts: ./references/standard-of-excellence.md Invented limit patterns: ./references/invented-limit-patterns.md BLOCKED declaration contract: ./references/blocked-declaration-contract.md
Workflow
flowchart TD
Start(["Task received"]) --> P1
P1["Read task-description argument<br>Scan affected files for TODO / FIXME / PENDING"] --> P2
P2{"Scope determinable?<br>Affected files, expected behavior, and<br>success criteria identifiable from request?"}
P2 -->|No| P2a["State assumption explicitly — then proceed"]
P2 -->|Yes| E1
P2a --> E1
E1{"About to build without searching?"}
E1 -->|Yes| E1a["Search first — confirm prior art before implementing"]
E1a --> E2
E1 -->|No — search done| E2
E2{"Considering a prohibited exit?<br>workaround / deferral / truncation<br>partial delivery / 'leave as exercise'"}
E2 -->|No| E3
E2 -->|Yes| E2a{"Permanent solve reachable?"}
E2a -->|Yes| E2b["Apply permanent solve — return to work"]
E2b --> E3
E2a -->|"No — named external constraint"| Blocked
E3{"Pre-existing issue found during work?"}
E3 -->|No| C1
E3 -->|Yes| E3a["'I found N pre-existing X.<br>Address now or add to backlog?'"]
E3a --> E3b{"User: address now?"}
E3b -->|Yes| E3c["Scope fix into current task — continue"]
E3b -->|No or no response| E3d["Create backlog record — continue"]
E3c --> C1
E3d --> C1
C1["Answer Dangling Thread Checklist"] --> C2
C2{"Open thread?<br>TODO / FIXME / partial impl /<br>untested behavior / invented limit?"}
C2 -->|Yes — thread unaddressed| P1
C2 -->|No — all clear| Done
Blocked["BLOCKED declaration:<br>reason + completed + remains<br>+ unblocking condition"]
Done(["Task complete"])
Preparation
Before applying any task, inspect the input:
- Read the
[task-description]argument if provided. - Identify whether prior partial work exists — check for TODO, FIXME, or PENDING markers in affected files.
- Confirm the task scope is understood: what files, what behavior, what "complete" looks like.
- If affected files, expected behavior, or success criteria cannot be determined from the request and context, state the assumption explicitly before proceeding.
This inspection takes under 60 seconds and prevents the most common failure mode: starting in the middle of something already broken.
The Standard
The marginal cost of completeness is near zero. Complete the whole thing.
- Search before building. Check whether the solution already exists before implementing.
- Test before shipping. Verify observable behavior, not just syntax correctness.
- Ship the complete thing. The answer is the finished product, not a plan to build it.
Time, fatigue, and complexity are not valid reasons to stop short.
Prohibited Exits
NEVER use the following exits when the permanent solve is reachable:
| Prohibited form | Why it fails | Required action |
|---|---|---|
| "We could table this for later" | Defers solvable work | If reachable now, solve it now |
| "As a workaround you could..." | Leaves root cause intact | Find and apply the real fix |
| "Here's a partial implementation" | Delivers incomplete value | Complete it, or declare BLOCKED (see below) |
content[:500], MAX_LEN = 1024 | Silent data loss | Output full content; let caller control the window |
| "I'll leave the rest as an exercise" | Delegates responsibility back | Do it |
The One Legitimate Exit — BLOCKED Declaration
When the permanent solve is genuinely unreachable due to an external constraint, use this form. Copy ./assets/blocked-declaration-template.md verbatim into your response and fill in every field. Full contract: ./references/blocked-declaration-contract.md
# WRONG — workaround instead of BLOCKED
The build fails because the dependency is missing. As a workaround,
comment out the import for now.
# RIGHT — specific constraint with actionable path
BLOCKED: fastmcp[tasks] is not in pyproject.toml and the file is read-only in CI.
- What was completed: identified failing import at src/runner.py:14
- What remains: add fastmcp[tasks] to pyproject.toml; run uv lock; re-run pytest tests/ -x
- Unblocking condition: pyproject.toml is writable and fastmcp[tasks] is in dependencies
No Invented Limits
NEVER introduce hard-coded truncation or length limits. Full taxonomy: ./references/invented-limit-patterns.md
Rules:
- Output full content by default.
- When pagination is genuinely needed, provide
--offset/--limitparameters. - If content is shortened: (1) state it is truncated, (2) report chars/lines remaining, (3) provide access to the rest.
Dangling Thread Protocol
Template: ./assets/dangling-thread-checklist.md — copy into your response as a structured self-review block, or work through it mentally before marking complete.
Before marking any task complete, answer each question:
- Is there an open thread — a TODO, FIXME, PENDING marker, partial implementation, or untested behavior?
- Is the current solution a workaround when the real fix exists?
- Was search performed before building anything new?
- Were tests run — or is there an explicit reason they cannot be?
- Does any output contain a hard-coded truncation or length limit?
If any question is answered yes and the thread is unaddressed, return to Preparation: scope the fix, apply it, then re-check before marking complete.
Task is complete when: all 5 checklist items answer "no" AND any BLOCKED declaration includes all four required fields AND any pre-existing issue is either resolved or logged as a backlog item.
Pre-Existing Issue Rule
When a pre-existing issue is found during a task, "pre-existing issue not related to my changes" is a trigger to act, not a dismissal.
Required response:
I found [N] pre-existing [issue type]. Want to address them now? If not, I will add them to the backlog.
"Plan" means concrete steps — files, fixes, scope estimate — not a vague intention. "Backlog" means a trackable record that prevents loss.
If the user responds "yes, address them now" → scope the fix into the current task and continue. If the user says no or does not respond → create the backlog record before proceeding.
Anti-Patterns
# WRONG — workaround presented as solution
The issue is that the config file is malformed. As a workaround, you can set
the ENV variable directly to bypass the config loader.
# RIGHT — root cause fixed
The config loader fails on empty string values (config.py:47).
Fixed: added a guard that converts empty strings to None before validation.
Tests pass. No ENV variable workaround needed.
# WRONG — invented limit silently truncates
return content[:500] # keep it brief
# RIGHT — full content, caller controls window
return content # caller applies display limit if needed
# WRONG — deferred completion
I've implemented the core logic. The edge cases and tests can be added later.
# RIGHT — complete delivery
Core logic implemented. Edge cases handled: [list]. Tests written and passing.
Sources
SOURCE: ./references/standard-of-excellence.md — verbatim extracts from .claude/CLAUDE.md §Standard of Excellence, §No Invented Limits, §Pre-Existing Issue Accountability. Extracted 2026-05-22.
Frequently asked questions
What to verify before installation and use
What does the boil source document cover?
Outcome: A task is complete only when all output is delivered (no prohibited exits taken, no workarounds), the Dangling Thread Checklist has no open items, and no PENDING threads remain.
How do I install boil?
The source record exposes this install command: npx skills add https://github.com/Jamie-BitFlight/claude_skills --skill ".claude/skills/boil". Inspect the command and pinned source before running it.
Alternatives
Compare before choosing
garrytan/gbrain
bulk-ingestion
End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.
alirezarezvani/claude-skills
app-store-optimization
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
citation-audit
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
prowler-cloud/prowler
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance