CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

eiirp

Everything In Its Right Place. The universal post-work organizer. After any significant work session, EIIRP runs a 7-phase audit: (1) inventory every output, (2) walk taxonomy to decide where each lands, (3) check schema-pack consistency against the brain's actual shape, (4) file enriched brain pages, (5) audit the skill graph for DRY+MECE, (6) verify resolvability, (7) report. Named after the Radiohead song. Nothing produced during significant work lives only in chat — knowledge becomes permanent, patterns become reusable. Also carries the always-on auto-fire gate: when >=500 words of structured analysis on a user-shared document is about to be delivered, file the brain page first, then deliver the analysis with the link in that same reply.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/eiirp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

An unusually actionable and well-sequenced operational manual: every phase has executable gbrain commands, explicit validation checkpoints, error-recovery guidance, and a machine-readable report format. The main costs are token weight — a duplicated report template, repeated gate statements, and an inline version-anchored changelog — in an otherwise clean single-file structure with well-signaled cross-skill references.

Suggestions

Delete the duplicate report template: the Phase 7 section and the Output Format section repeat nearly the same '## EIIRP Complete' block — keep one and cross-reference it.

Move the Changelog (and its version-pinned details like 'v0.39 cathedral', 'v0.19 resolver') into a CHANGELOG.md reference file or trim it to one line per version, keeping SKILL.md free of time-sensitive version detail.

Consolidate the auto-fire gate rule, currently restated in the Contract, the gate section, Anti-Patterns, and Hard Rules, into the gate section with one-line pointers from the other three.

DimensionReasoningScore

Conciseness

The body is mostly procedural and command-driven, but carries real fat: the Phase 7 report template appears twice nearly verbatim ("## EIIRP Complete: [Topic]" in Phase 7 and again in Output Format), the auto-fire gate rule is restated four-plus times (Contract, gate section, Anti-Patterns, Hard Rules), and a changelog with version-specific detail ("gbrain v0.39.0.0", "the v0.19 resolver") pads the tail. Not 2 because there is no explaining of concepts Claude already knows and most sections earn their tokens; not 4 because the duplication and changelog bulk are more than minor.

3 / 5

Actionability

Every phase ships copy-paste-ready commands: "gbrain schema show --json", "gbrain capture --file <analysis.md> --slug <taxonomist-path>", "gbrain schema review-candidates --apply <prefix-or-type-name>", "gbrain check-resolvable", plus concrete templates (manifest, filing-plan table, Phase 7 report) and explicit thresholds like "confidence < 0.6... DO NOT auto-apply". Fully executable with specific examples covering the common cases.

5 / 5

Workflow Clarity

The 7 phases are clearly sequenced with a dedicated verification phase (Phase 6 checklist: "All brain pages have proper frontmatter", "gbrain orphans — any pages without inbound links?"), mid-flow validation (Phase 4c "Verify every link resolves"), a human-in-the-loop confidence gate in Phase 3, and explicit error-recovery loops in "When it fails" ("revision_conflict or write_pending (exit 10): re-read and merge, or poll gbrain write-request <request_id>"). Batch brain-writes are fully covered by validation, so no cap applies.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ all absent), so all content is inline, but the single file is well-organized with numbered phase sections, checklists, and clearly signaled one-level-deep cross-skill references ("skills/brain-taxonomist/SKILL.md", "../conventions/brain-first.md", "skills/meeting-ingestion/SKILL.md") that all resolve as named sibling skills. Not 5 because ~460 lines of changelog, gate policy detail, and the duplicated report template are inlined in SKILL.md where a reference file split would ease navigation; not 3 because references that do exist are clearly signaled and the structure is consistently good.

4 / 5

Total

17

/

20

Passed

Description

67%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.

A detailed, third-person description that clearly answers "what" with an enumerated 7-phase audit and the auto-fire gate, and gives explicit timing for "when". Its weaknesses are missing natural trigger phrases in the description text itself and some internal jargon (schema-pack, resolvability, DRY+MECE) that blurs concreteness for an outside reader.

Suggestions

Add a closing 'Use when...' sentence with concrete trigger phrases (e.g., "Use after a deep research or build session, or when the user says 'organize this work', 'file this research', or 'make this re-doable'") so natural keywords live in the description itself, not only the triggers list.

Trim flavor text ("Named after the Radiohead song", "The universal post-work organizer") and replace jargon like "check schema-pack consistency against the brain's actual shape" with a plainer action verb phrase.

State the distinction from sibling skills (ingest, taxonomist) in one clause inside the description to reduce overlap risk on broad terms like 'deep analysis' and 'review this report'.

DimensionReasoningScore

Specificity

The description enumerates concrete actions: "runs a 7-phase audit: (1) inventory every output, (2) walk taxonomy to decide where each lands, (3) check schema-pack consistency... (4) file enriched brain pages, (5) audit the skill graph for DRY+MECE, (6) verify resolvability, (7) report" plus the auto-fire gate behavior. Not score 5 because several actions lean on internal jargon ("schema-pack consistency against the brain's actual shape", "verify resolvability") whose concrete meaning is unclear to a fresh reader; not 3 because far more than 1-2 concrete actions are named.

4 / 5

Completeness

"What" is explicit and detailed (7-phase audit enumerated plus the auto-fire gate), and "when" is stated — "After any significant work session" — plus "when >=500 words of structured analysis on a user-shared document is about to be delivered" for the gate. Not 5 because there is no "Use when..." clause with concrete trigger phrases in the description itself; not 3 because the when-guidance is explicit timing, not merely implied.

4 / 5

Trigger Term Quality

The description itself offers only a few relevant keywords — "post-work organizer", "After any significant work session", "Everything In Its Right Place" — and misses the natural phrases users would actually say ("organize this work", "file this research", "store this"). Not 4 because common natural variations are absent from the description text (they live in the separate frontmatter triggers list, which is not the evaluation target); not 2 because the timing keyword "after any significant work session" is genuinely relevant.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — post-work filing into a personal "brain" knowledge base plus a skill-graph DRY/MECE audit — with specific differentiators like "Nothing produced during significant work lives only in chat — knowledge becomes permanent, patterns become reusable". Not 5 because "The universal post-work organizer" is a broad claim and the description does not delineate itself from adjacent ingestion/filing skills (that work is done by the frontmatter distinct_from list, not the description).

4 / 5

Total

15

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (541 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

garrytan/gbrain

Path

skills/eiirp/SKILL.md

Reviewed

Table of Contents

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.