CtrlK
BlogDocsLog inGet started
Tessl Logo

add-pattern

Use this skill when you learn one or more design pattern(s) in the Langroid (multi) agent framework, and want to make a note for future reference for yourself. Use this either autonomously, or when asked by the user to record a new pattern.

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/langroid/skills/add-pattern/SKILL.md
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 concise, well-structured instruction skill that tells Claude exactly which files to touch and what format to follow, appropriately pointing to existing pattern files rather than duplicating them. The main gap is the absence of an inline example entry and a small amount of unspecified guidance around category selection and reference validation.

Suggestions

Include a short inline example of a patterns/SKILL.md entry (a DESCRIPTION line plus a '- Reference:' pointer) so the format is unambiguous without requiring Claude to open an existing file first.

Add a brief note on how to choose the 'appropriate category section', or point to where the category list lives, since that step is currently underspecified.

Add a light verification checkpoint, e.g. 'confirm the - Reference: path resolves to the document you created', to close the workflow loop.

DimensionReasoningScore

Conciseness

Lean and efficient: it assumes Claude knows what Langroid and design patterns are, states the two actions without padding, and every line (including the IMPORTANT note on description quality) earns its place.

5 / 5

Actionability

Gives concrete guidance — the exact file (sibling patterns/SKILL.md), the entry structure (DESCRIPTION + '- Reference:' pointer), and the document format (Problem, Solution, Complete Code Example, Key Points, When to Use) — but defers the example shape to 'existing pattern files' without an inline template.

4 / 5

Workflow Clarity

A clear two-step numbered sequence (add entry, then write the reference document) for a simple single-purpose skill, with a minor gap: 'appropriate category section' is unspecified and there is no checkpoint verifying the reference pointer resolves.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and clearly signaled, one-level-deep references to the sibling patterns/SKILL.md and patterns/ directory; meets the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

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

The description clearly answers both what and when with an explicit, niche-scoped trigger tied to the Langroid framework. Its main weakness is that the 'what' lists only a single generic action ('record/note a pattern') rather than the concrete steps the skill performs.

Suggestions

Replace the generic 'make a note for future reference' with the concrete actions the skill performs, e.g. 'add an entry to patterns/SKILL.md and create a reference document describing the pattern with code examples'.

Mention the expected document format briefly (Problem / Solution / Code Example) so the 'what' is more specific and self-contained.

DimensionReasoningScore

Specificity

Names the domain clearly ('Langroid (multi) agent framework' design patterns) and one concrete action ('record a new pattern' / 'make a note for future reference'), but does not enumerate the multiple sub-actions the skill actually performs.

3 / 5

Completeness

Explicitly states both what ('record a new pattern' / 'make a note for future reference') and when ('Use this skill when you learn one or more design pattern(s)... autonomously, or when asked by the user'), but the 'what' is a single generic action rather than a comprehensive list.

4 / 5

Trigger Term Quality

Includes natural terms a Langroid user would say — 'design pattern(s)', 'Langroid', 'agent framework', 'record a new pattern', 'make a note' — with good coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to Langroid design-pattern recording, a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pchalasani/claude-code-tools
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.