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.

57

Quality

65%

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

65%

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 clearly directs editing a sibling file and creating a templated document, but it lacks a concrete example entry and any verification step. Referenced sibling files are not present in the bundle to confirm the disclosure structure.

Suggestions

Add a short concrete example showing a sample patterns/SKILL.md entry and a matching reference document to make the guidance copy-paste ready.

Specify how to pick the "appropriate category section" (e.g., list the categories or the rule for choosing one) to remove ambiguity.

Add a brief verification step (e.g., confirm the reference path resolves and the entry matches the existing format) before finishing.

DimensionReasoningScore

Conciseness

The body is lean and instruction-focused with no concept explanations Claude already knows; every line directs an action and earns its place.

3 / 3

Actionability

Gives concrete file targets (sibling patterns/SKILL.md), a - Reference: pointer structure, and a section template, but provides no concrete example entry to model from, leaving key details implicit.

2 / 3

Workflow Clarity

The two steps are numbered and sequenced, but there is no validation/verification checkpoint and the "appropriate category section" choice is left ambiguous for the writer.

2 / 3

Progressive Disclosure

The short body is well-organized and references one-level-deep sibling patterns/ files, but those referenced files are not present in the bundle to verify structure or navigation.

2 / 3

Total

9

/

12

Passed

Description

65%

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 is well-targeted to a clear niche with explicit what-and-when guidance, but loses specificity points for second-person voice and somewhat limited action vocabulary. Trigger term coverage is adequate rather than comprehensive.

Suggestions

Rewrite the description in third person (e.g., "Records Langroid design patterns for future reference") to avoid the specificity penalty and avoid second-person voice.

Expand the action vocabulary to list multiple concrete operations (e.g., categorize, document with code examples, link reference docs) to lift specificity above 2.

Broaden trigger terms to include natural user phrasings like "Langroid pattern", "agent pattern", or "reusable agent design".

DimensionReasoningScore

Specificity

Names the Langroid domain and a couple of actions ("make a note for future reference", "record a new pattern") which would anchor at 2, but the description is written in second person ("Use this skill when you learn...") which the rubric penalizes by reducing specificity by 1.

1 / 3

Completeness

Clearly answers both what (note/record a Langroid design pattern) and when (when you learn one, autonomously or when asked) with explicit triggers.

3 / 3

Trigger Term Quality

Includes relevant terms ("Langroid", "design pattern", "record a new pattern") and an explicit "Use this skill when..." trigger, but lacks common natural variations a user might say.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear narrow niche (Langroid framework design patterns) with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

9

/

12

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.