CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autonomous-agents

You are an agent architect who has learned the hard lessons of autonomous AI. You've seen the gap between impressive demos and production disasters. You know that a 95% success rate per step means only 60% by step 10.

28

Quality

35%

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/AI-Agents-Safe-Coding-Skills-claude/skills/autonomous-agents/SKILL.md

The canonical home for this skill is autonomous-agents in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

30%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 a skeletal outline posing as a skill: section scaffolding exists, but the substance is placeholder-grade — an intro cut off mid-sentence, empty anti-pattern headings, a Sharp Edges table whose Issue column literally reads 'Issue', and generic one-line descriptions of patterns Claude already knows. There is no actionable guidance, no sequenced workflow, and no validation anywhere.

Suggestions

Replace the Anti-Patterns stubs ('❌ Unbounded Autonomy' etc.) with concrete content: for each anti-pattern state what to do instead, e.g. '❌ Unbounded Autonomy → cap loop iterations (e.g. 10), set a token/cost budget, and require a success check before each autonomy level increase.'

Add a sequenced workflow with validation checkpoints, e.g. '1. Define a single constrained task for the agent; 2. Run it N times and record per-step success rate; 3. Only if reliability > threshold, add the next capability; 4. Re-measure after each change.'

Fix the corrupted content: complete the truncated sentence ('logging befor…'), fill the Sharp Edges table's Issue column with real failure modes instead of the literal text 'Issue', and remove the stray '##' prefixes from the Solution column entries.

DimensionReasoningScore

Conciseness

The body is short and not padded, but it spends tokens restating concepts Claude already knows — one-liners like 'Alternating reasoning and action steps', 'Self-evaluation and iterative improvement' for ReAct/plan-execute/reflection — plus a broken Sharp Edges table whose Solution column holds stray heading fragments ('## Reduce step count'). This matches anchor 3 ('mostly efficient but includes some unnecessary explanation'); it is leaner than anchor 2's padded verbosity but not the every-token-earns-its-place quality of anchor 5.

3 / 5

Actionability

There is no code, no command, and no executable step anywhere; the most concrete content is the Sharp Edges table's terse directives ('Set hard cost limits', 'Least privilege principle', 'Track context usage') and the Anti-Patterns section, which lists three headings ('Unbounded Autonomy', 'Trusting Agent Outputs', 'General-Purpose Autonomy') with no explanation of what to do instead. This fits anchor 2 ('high-level hints but missing the specific steps to execute') rather than anchor 1, since the table rows do name concrete mitigations even without steps.

2 / 5

Workflow Clarity

No multi-step process is ever sequenced — there is no numbered or ordered workflow, no validation checkpoint, and no feedback loop anywhere in the body. The 'When to Use' section is circular ('This skill is applicable to execute the workflow or actions described in the overview') and the intro sentence is literally truncated mid-word ('logging befor'), matching anchor 1 ('steps missing or incoherent; no sequence; no validation').

1 / 5

Progressive Disclosure

The body has real section structure (Capabilities, Patterns, Anti-Patterns, Sharp Edges, Related Skills, When to Use) and no bundle files exist to reference, so nothing needs offloading. However the structure is undermined by empty Anti-Patterns subsections, a placeholder-filled table, and the truncated intro — organized-but-could-be-better matches anchor 3; it is not the monolithic/un-navigable anchor 1-2 case, nor the well-signaled clarity of anchor 4-5.

3 / 5

Total

9

/

20

Passed

Description

11%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 is a persona vignette rather than a capability description: it establishes a voice and one reliability statistic but never states what the skill does or when to invoke it, and it is written in second person. It would almost never be selected by trigger matching because it contains no action verbs or trigger phrases.

Suggestions

Rewrite the description in third person listing concrete actions, e.g. 'Designs reliable autonomous agents: decomposes goals, adds guardrails and cost limits, structures agent loops (ReAct, plan-execute, reflection), and hardens agents against compounding step-failure rates.'

Add an explicit trigger clause: 'Use when building, debugging, or hardening autonomous agents, agent loops, or long-horizon agent workflows, or when agent reliability/success-rate degradation is a concern.'

Drop the persona narrative ('You are an agent architect...') and the demo-vs-disaster framing — they consume the entire description budget without adding a single triggerable keyword.

DimensionReasoningScore

Specificity

The description lists no concrete actions at all — it is pure persona narrative ("You are an agent architect who has learned the hard lessons of autonomous AI", "You've seen the gap between impressive demos and production disasters") with zero capability statements. It also uses second person ("You are", "You know"), which per the guidelines further penalizes specificity, and anchor 1 ("pure abstract language") is the best fit; anchor 2 would require at least naming a domain with minimal actions.

1 / 5

Completeness

Neither 'what does this skill do' (no capability or action is ever described — the reader learns only that some architect 'knows' a statistic) nor 'when to use it' (no 'Use when...' clause or equivalent trigger guidance exists) is answered. Both are effectively missing, matching anchor 1; the missing-use-when cap of 3 is irrelevant since the 'what' is absent too.

1 / 5

Trigger Term Quality

The only domain keyword present is "autonomous AI"; there are no natural trigger phrases a user would say (no "agent reliability", "agent loops", "autonomous agents", or any 'use when' phrasing). This sits between anchor 1 (no natural keywords, only abstract narrative) and anchor 2 (one or two generic keywords missing the natural phrases), matching anchor 2's 'generic keyword without natural phrasing' character.

2 / 5

Distinctiveness Conflict Risk

The generic persona framing ("autonomous AI", "agent architect", "production disasters") overlaps heavily with any agent-design, agent-ops, or reliability skill, and nothing distinguishes it from siblings like multi-agent-orchestration or agent-evaluation. It is not entirely generic enough for anchor 1, but 'very broad; high overlap risk with many similar skills' (anchor 2) fits well.

2 / 5

Total

6

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/autonomous-agents/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.