test-skill

A test skill with resources

Quality

28%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crates/forge_repo/src/fixtures/skills_with_resources/test-skill/SKILL.md

Quality

Content

22%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 body is an essentially empty placeholder: one heading and one declarative sentence. It is not verbose, but it provides no actionable guidance, no workflow, and no meaningful structure or references.

Suggestions

Add concrete, executable guidance (code or specific commands) so the skill is actionable when invoked.

If the skill is genuinely multi-step, document the sequenced workflow with explicit validation checkpoints.

Give the overview body real substance or, for a simple skill, ensure the single action is stated unambiguously so workflow clarity is not absent.

Dimension	Reasoning	Score
Conciseness	The body "This is a test skill." is lean with no padding or over-explanation, but the tokens convey no substantive value, so it is efficient yet content-empty rather than earning their place.	3 / 5
Actionability	The body gives only a descriptive sentence with no concrete code, commands, or steps, matching the entirely-vague/abstract anchor.	1 / 5
Workflow Clarity	No steps, sequence, or validation are present; the body states only "This is a test skill," so the workflow is absent.	1 / 5
Progressive Disclosure	A single "# Test Skill" header provides minimal structure with no references, and as a trivial under-50-line skill this is acceptable but only weakly organized.	3 / 5
	Total	8 / 20 Passed

Description

0%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 minimal placeholder that names no concrete capabilities, includes no trigger terms, and provides no usage guidance. It scores at the floor on every dimension.

Suggestions

Replace "A test skill with resources" with concrete verbs naming what the skill does (e.g., "Extracts text from PDF files, fills forms, merges documents").

Add an explicit "Use when..." clause listing natural trigger phrases a user would actually say.

Include relevant file extensions or synonyms (e.g., .pdf, PDFs) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description "A test skill with resources" names no concrete actions and uses purely abstract language, matching the entirely-vague anchor.	1 / 5
Completeness	Both the "what" (vague: "test skill with resources") and the "when" (entirely absent) are missing or extremely vague, hitting the lowest anchor.	1 / 5
Trigger Term Quality	No natural keywords a user would say appear; "resources" is entirely generic and contains no domain trigger terms.	1 / 5
Distinctiveness Conflict Risk	The phrasing is entirely generic and would overlap with virtually any skill, offering no distinguishable trigger.	1 / 5
	Total	4 / 20 Passed

Validation

100%

Warnings & errors only

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: tailcallhq/forgecode
Path: crates/forge_repo/src/fixtures/skills_with_resources/test-skill/SKILL.md
Commit: 8eb3e24

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.