CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentica-prompts

Write reliable prompts for Agentica/REPL agents that avoid LLM instruction ambiguity

Quality

64%

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 ./.claude/skills/agentica-prompts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with reusable templates and tables, but it over-explains via speculative stats and citations and inlines template bulk that would benefit from reference files. The orchestration workflow has a clear sequence but lacks explicit validation checkpoints.

Suggestions

Trim the prose intro, the speculative "Expected Improvement" percentages, and the "References" citations block to lift conciseness toward a 4-5.

Make the VALIDATE and REVIEW orchestration steps explicit with commands or checklists and a fix-and-retry feedback loop (e.g., "if validation fails, revise the plan and re-validate") to move workflow clarity above 3.

Move the pattern-specific prompt templates into a single one-level-deep reference file (e.g., references/templates.md) referenced from a concise overview, and include one fully-filled worked example to push both progressive_disclosure and actionability higher.

DimensionReasoningScore

Conciseness

The prompt templates and tables are lean, but the prose intro ("Standard natural language prompts fail ~35% of the time..."), the speculative "Expected Improvement" stats, and the citations "References" section add unnecessary padding Claude doesn't need, matching the anchor for mostly efficient with some unnecessary explanation.

3 / 5

Actionability

It supplies multiple copy-paste-ready prompt templates (Coordinator, Generator, Critic, Juror, Swarm), a verb-mapping table, anti-patterns, and executable Python/bash snippets, with only the minor gap that templates use unfilled placeholders rather than a worked end-to-end example.

4 / 5

Workflow Clarity

The Orchestration Pattern is a clear 6-step sequence, but the VALIDATE and REVIEW steps are single-line descriptions with no explicit validation commands, outputs, or fix-and-retry feedback loops, so checkpoints are present but only implicit for a fragile multi-agent process.

3 / 5

Progressive Disclosure

The body is well-sectioned with headers but is ~250 lines of inlined full prompt templates with no one-level-deep reference files to offload the bulk, and no bundle files exist; this fits the anchor for some structure with content that could be split into separate files.

3 / 5

Total

13

/

20

Passed

Description

53%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 names a concrete domain and action but lacks any explicit "when to use it" guidance, which caps its completeness. Trigger terms are present but lean on jargon rather than natural user phrasing.

Suggestions

Add a "Use when..." clause with concrete trigger phrases (e.g., "Use when writing prompts for Agentica/REPL agents, when an agent isn't following instructions, or when designing multi-agent system prompts").

Replace jargon like "LLM instruction ambiguity" with natural terms a user would say (e.g., "prompts that agents reliably follow", "prompts that don't get misinterpreted").

List 1-2 more concrete actions (e.g., "designs multi-agent system prompts, adds explicit verb mappings, structures directory handoffs") to lift specificity toward a 4-5.

DimensionReasoningScore

Specificity

Names the domain ("Agentica/REPL agents") and one concrete action ("Write reliable prompts... that avoid LLM instruction ambiguity") but offers no list of multiple specific actions, matching the anchor for naming a domain plus 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

It states a clear "what" (write reliable prompts that avoid ambiguity) but provides no "Use when..." clause or any explicit trigger guidance for when to invoke the skill, so per the guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains a few relevant keywords ("prompts", "Agentica/REPL agents") but leans on technical jargon ("LLM instruction ambiguity") and misses the natural phrases a user would actually say, fitting the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

The "Agentica/REPL agents" framing carves out a fairly specific niche with only minor overlap risk against general prompt-writing skills, but it stops short of spelling out distinct trigger phrases that would justify a 5.

4 / 5

Total

13

/

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

parcadei/Continuous-Claude-v3

Path

.claude/skills/agentica-prompts/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.