CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-execution-receipts

Inspect signed Codex execution receipts, import provider audit events, and explain whether an action has local evidence, a candidate correlation, or a provider binding.

67

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, token-efficient instruction skill with a concrete sequenced procedure and an explicit validation checkpoint; the only notable gap is the absence of an error-recovery feedback loop.

DimensionReasoningScore

Conciseness

Lean and efficient: a single trigger line, a tight 5-step procedure, and one guardrail line, with no padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Concrete, specific guidance — named app/file ('Cerebro Agent Receipts app', 'receipts.ndjson'), named API call ('CloudTrail LookupEvents'), and named checks (account, role, action ID, action, time) — with minor gaps in the exact mechanism for signature/digest verification.

4 / 5

Workflow Clarity

A clearly numbered 5-step sequence with an explicit validation checkpoint (step 2 verifies signatures and the digest chain), but it lacks an explicit error-recovery feedback loop for what to do when verification fails.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and clean section structure (heading + Procedure), satisfying the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

75%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 specific, distinctive description that concretely names the skill's actions and classification states, but it omits any explicit 'when to use' trigger clause, which caps its completeness.

Suggestions

Append a 'Use when...' clause naming the natural trigger phrases (e.g., 'Use when the user asks who ran a command, whether an agent action reached a provider, or which changes lack provider attribution') to lift completeness above 3.

Add one or two common-sense synonyms or phrasings alongside the technical terms so users not steeped in the system's vocabulary still match the skill.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Inspect signed Codex execution receipts', 'import provider audit events', and 'explain' a three-state classification (local evidence / candidate correlation / provider binding) — giving comprehensive coverage of the skill's purpose.

5 / 5

Completeness

It clearly states 'what' the skill does but includes no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Domain-natural keywords ('execution receipts', 'provider audit events', 'local evidence', 'provider binding') are relevant and would be used by a user of this system, though a few lay synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The niche — correlating signed agent receipts with provider audit events — is highly specific with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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
writer/cerebro
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.