CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentfolio

Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/agentfolio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 content is a well-structured, actionable guide with a clear workflow, concrete evaluation criteria, and honest limitations, scoring solidly on actionability, workflow clarity, and organization. Its main weakness is moderate verbosity — the intro, Capabilities, and When to Use sections overlap noticeably and could be consolidated.

Suggestions

Merge the intro "This skill helps you" bullets with the "Capabilities" section — they currently repeat the same discover/compare/research points — and drop the decorative "Role:" line.

Trim "How to Use" step 2's example search phrases and the "When to Use" section down to a short trigger list, since the trigger conditions are already implied by the intro.

Optionally move the three "Example Workflows" into a references file (e.g. workflows.md) to keep SKILL.md a lean overview with well-signaled, one-level-deep navigation.

DimensionReasoningScore

Conciseness

The body is mostly efficient but has avoidable repetition: the intro bullets ("Find existing agents before building your own from scratch") and the "Capabilities" section ("Discover autonomous AI agents... Compare agents...") restate the same points, and step 2 explains how to search with example keywords — something Claude can infer. Fits 'mostly efficient but could be tightened'; not a 4 because the duplicate bullets and the decorative "Role:" line are clear trim candidates.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete: specific evaluation fields (core promise, input/output shape, autonomy model, deployment model), named comparison-table columns (capabilities, integrations, pricing, trust & security), example search queries, and ready-to-use example prompts. Not a 5 because some steps remain directional ("Verify current pricing/licensing... against the vendor's primary documentation") without a concrete capture or output format.

4 / 5

Workflow Clarity

The four-step "How to Use" sequence (open directory, search by intent, evaluate candidates, synthesize insights) is clearly ordered and includes checkpoints such as verifying pricing/benchmarks against vendor docs and "mark missing information rather than inventing capabilities". Not a 5 because there are no explicit error-recovery or re-verification loops (e.g., what to do when directory data is stale mid-workflow) — though the read-only research nature means the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

The single-file structure is well organized with clear sections (Capabilities, How to Use, Example Workflows, Example Prompts, When to Use, Limitations) and no external bundle files exist, so nothing is buried or nested. Not a 5 because at ~93 lines with some content (capabilities/workflow duplication, example prompt lists) that could either be trimmed or split into a reference file for leaner top-level navigation.

4 / 5

Total

15

/

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 clearly states what the skill does and anchors it to a specific directory, giving it reasonable distinctiveness. However, it lacks any 'Use when...' trigger guidance, omits natural user phrasings like "find" or "compare agents", and offers only two broad actions, leaving it at the middle of the scale.

Suggestions

Add an explicit 'when' clause, e.g. "Use when the user wants to find, compare, or research autonomous AI agents, agent frameworks, or agent tools instead of building one from scratch."

Include natural trigger synonyms such as "find agents", "compare AI agents", "agent frameworks", and "agent directory" so users' everyday phrasing matches the description.

Make the actions slightly more concrete, e.g. "discovers, compares, and researches autonomous AI agents, frameworks, and tools using the AgentFolio directory".

DimensionReasoningScore

Specificity

"discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory" names the domain (agent directory) and two actions (discover, research), matching the 'names domain and 1-2 concrete actions' anchor. Not a 4 because 'discovering' and 'researching' are broad verbs with no narrower concrete operations listed; not a 2 because two real actions plus a specific tool are named rather than minimal or generic phrasing.

3 / 5

Completeness

The 'what' is stated clearly (discover and research agents via the AgentFolio directory) but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. This exactly matches anchor 3: clear 'what', missing 'when'.

3 / 5

Trigger Term Quality

Keywords like "autonomous AI agents", "tools", and "ecosystems" are relevant, but common user phrasings are missing: no "find", "compare", "agent frameworks", "agent directory", or a 'Use when...' trigger clause. Fits 'some relevant keywords but missing common variations or synonyms'; not a 4 since natural-term coverage has real gaps, not just a few.

3 / 5

Distinctiveness Conflict Risk

Anchoring the skill to the "AgentFolio directory" gives it a clear niche that is mostly distinct from other skills, but "tools, and ecosystems" keeps it broad enough for minor overlap with general research/discovery skills. Not a 5 because the trigger terms themselves are not distinct enough to guarantee minimal conflict risk.

4 / 5

Total

13

/

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

sickn33/agentic-awesome-skills

Path

skills/agentfolio/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.