add-example-agent

Add a new self-contained example agent under examples/. Use when asked to "create an example for <framework>", "add a tutorial agent", "demo integration with <LLM provider>", or when showcasing a new pattern users should copy.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/add-example-agent/SKILL.md

Quality

Content

75%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-structured, actionable skill body with a clear sequenced workflow and an explicit validation step. It scores consistently at 4 across dimensions, held back only by minor over-explanation, a stubbed handler body, a missing error-recovery branch, and some inline content that could be externalized.

Suggestions

Add an explicit error-recovery loop in Step 6 (e.g., "If no response or signature is missing, fix the handler/config and re-run the curl test before committing") to reach the top workflow-clarity anchor.

Trim the justificatory clauses in the Overview and "Never do" sections (e.g., "so inconsistency hurts discoverability") to push conciseness to the lean anchor.

Show a minimal complete handler body for one framework (or link to a template handler) so the wiring example is fully copy-paste ready rather than a `...` stub.

Dimension	Reasoning	Score
Conciseness	Mostly lean imperative style with no explaining of concepts Claude already knows; minor over-explanation remains in the Overview rationale ("so inconsistency hurts discoverability") and the "Never do" justification clauses that could be trimmed.	4 / 5
Actionability	Provides a concrete directory tree, typed handler signatures, exact install/run commands, and a copy-paste curl test; the only gap is the handler body shown as a `...` stub, leaving it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	A clear six-step Execution Contract elaborated with numbered sub-steps and an explicit validation checkpoint (Step 6 with a success criterion); the destructive/batch cap does not apply since validation exists, but there is no explicit error-recovery branch, capping it at 4.	4 / 5
Progressive Disclosure	No bundle files exist, but external references are well-signaled one-level-deep markdown links and the body is cleanly sectioned; the verbose curl test block and template listing are kept inline rather than split into a referenced file, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

82%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 strong description: it states a concrete action, gives multiple natural trigger phrases, and explicitly covers both what and when. The only soft spot is specificity, which lists one action rather than the full set of sub-tasks the body performs.

Dimension	Reasoning	Score
Specificity	Names the domain ("a new self-contained example agent under examples/") and one concrete action (add), but does not enumerate the several sub-actions the body later covers, so it stops at the 1-2-actions anchor rather than the multi-action anchor.	3 / 5
Completeness	Explicitly answers both what ("Add a new self-contained example agent under examples/") and when ("Use when asked to …") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Quotes several natural phrases a user would actually say — "create an example for <framework>", "add a tutorial agent", "demo integration with <LLM provider>" — giving good keyword coverage, though no synonyms or file extensions push it to the top anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (authoring example/tutorial agents) with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 10 suspicious	Warning

	Total	15 / 16 Passed

Repository: GetBindu/Bindu
Path: .agents/skills/add-example-agent/SKILL.md
Commit: 7d5b6d2

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.