CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-skills-feedback

File a bug report or feedback on the Antithesis skills by opening a pre-filled GitHub issue URL (skill name, skill version, agent, short summary). Load when the user wants to report a problem with, or give feedback on, any Antithesis skill. Does not auto-submit — presents the URL for the user to review.

Quality

97%

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

92%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 tight, highly actionable single-file skill: it gives the exact URL, every template parameter with what to fill, the precise git command for the version, encoding rules, a length-limit fallback hierarchy, and a worked example, ending with an explicit do-not-auto-submit presentation step. The only weakness is minor duplication between the parameter table and the numbered steps, which costs a little token efficiency.

Suggestions

Remove the sentence-length guidance ('1-2 sentences', '2-4 sentences max') from either the parameter table or the numbered steps — stating it once would cut duplication and save tokens.

Trim the justification sentence 'Browsers and GitHub may truncate or reject longer URLs' to just the bolded 2000-character rule, since the limit itself is the actionable instruction.

DimensionReasoningScore

Conciseness

The body is lean overall — a parameter table, an assembly checklist, and a worked example — but the table's 'What to fill' column duplicates the numbered steps (e.g., '1-2 sentences' for what-happened and '2-4 sentences' for agent-explanation appear in both places), and 'Browsers and GitHub may truncate or reject longer URLs' is mildly padded. Minor trimming would reach the top anchor.

4 / 5

Actionability

Fully executable guidance: the exact base URL, a parameter table with field types, the exact command `git -C <skills-repo> rev-parse --short HEAD`, explicit percent-encoding rules, and a complete copy-paste-ready example URL that covers the common case.

5 / 5

Workflow Clarity

Eight clearly sequenced construction steps plus an explicit URL-length validation with an ordered degradation fallback (shorten what-happened/agent-explanation, then drop agent-explanation, then drop what-happened) and a human-review checkpoint ('Do NOT auto-submit the issue... so the user can review'). The operation is non-destructive, so no validation cap applies.

5 / 5

Progressive Disclosure

A simple single-purpose skill with no bundle files: all content appropriately lives in SKILL.md under well-organized, clearly headed sections (Base URL, Pre-filling fields, How to construct, URL length limit, Example URL, Presenting to the user) with nothing buried. Per the simple-skill guideline this earns the top score without external references.

5 / 5

Total

19

/

20

Passed

Description

100%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 model description: concrete third-person actions with the pre-filled fields enumerated, an explicit 'Load when...' trigger clause using natural user phrasing (report a problem, give feedback, bug report), a clear scope limited to Antithesis skills, and an honest boundary statement ('Does not auto-submit'). Concise with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'File a bug report or feedback... by opening a pre-filled GitHub issue URL (skill name, skill version, agent, short summary)' — and even enumerates the pre-filled fields, plus 'Does not auto-submit — presents the URL for the user to review'. Coverage is comprehensive for this narrow task with no material gaps.

5 / 5

Completeness

Explicitly answers both what ('File a bug report... by opening a pre-filled GitHub issue URL') and when ('Load when the user wants to report a problem with, or give feedback on, any Antithesis skill') with concrete trigger phrases, matching the top anchor rather than the merely-adequate 4 anchor.

5 / 5

Trigger Term Quality

The trigger clause 'Load when the user wants to report a problem with, or give feedback on, any Antithesis skill' plus 'bug report' covers the three natural phrasings a user would actually say. This is comprehensive synonym coverage for the domain (file extensions are not applicable here).

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — bug reports/feedback specifically on Antithesis skills via a GitHub issue — so triggers are distinct and overlap risk with other skills is minimal.

5 / 5

Total

20

/

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

antithesishq/antithesis-skills

Path

antithesis-skills-feedback/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.