CtrlK
BlogDocsLog inGet started
Tessl Logo

gini-bug-report

File a locally-captured, already-redacted Gini crash report as a GitHub issue, with the user's consent. Reads the pending crash queue and delegates the actual filing to the github-issues skill.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

A highly actionable, well-sequenced orchestration skill with executable code, strong validation checkpoints, and clean single-file organization. The only notable weakness is mild redundancy between the step bodies and the closing Rules checklist.

Suggestions

Trim the Rules section to non-obvious invariants not already stated inline (e.g. keep the token-handling and #N-quoting rules, drop the restated fingerprint-matching rule) to reduce repetition.

DimensionReasoningScore

Conciseness

The body is dense and avoids explaining concepts Claude already knows, but the Rules section restates the fingerprint-matching and redaction guidance from steps 2 and 3, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready bash and jq snippets with concrete --repo flags and exact field names, matching the top anchor.

3 / 3

Workflow Clarity

A clearly numbered five-step sequence with explicit validation checkpoints (dedup-first search, gh auth status re-verify, only-proceed-when-valid, resolve-after-decision-final) and feedback loops for an outward-facing filing operation.

3 / 3

Progressive Disclosure

Self-contained with no bundle files; well-organized into clearly signaled sections and a single one-level-deep delegation to the github-issues skill via read_skill, so navigation is easy.

3 / 3

Total

11

/

12

Passed

Description

82%Weight 40%Scale 1-3

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, well-scoped description with concrete actions and natural trigger terms, written in correct third-person voice. Its main weakness is the absence of an explicit "Use when..." trigger clause, which leaves the invocation timing implied rather than stated.

Suggestions

Append an explicit "Use when..." clause, e.g. "Use when the crash-report consent flow asks whether to file a captured Gini crash, or when the user explicitly asks to report one."

Add common trigger phrasings users might say ("file that crash", "report the crash") to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "File a locally-captured, already-redacted Gini crash report as a GitHub issue", "Reads the pending crash queue", "delegates the actual filing to the github-issues skill" — matching the top anchor.

3 / 3

Completeness

Clearly states what the skill does, but lacks an explicit "Use when..." trigger clause; the "with the user's consent" condition only implies when, capping completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Uses natural terms a user would say ("crash report", "GitHub issue", "consent", "crash queue") with good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (consent-aware filing of locally-captured Gini crashes) and explicitly scopes to delegating filing to github-issues, making conflict with other skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Open-Curiosity/gini-agent
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.