my-custom-skill

Example custom agent skill — a template to get started.

2.41x

Quality

50%

Does it follow best practices?

Impact

82%

2.41x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/agentsociety2/agentsociety2/custom/skills/examples/my-custom-skill/SKILL.md

Quality

Content

75%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 lean, well-structured instructional document: it documents two concrete skill patterns with system-specific details and closes with a worked example that makes the intended agent workflow unambiguous. Its main weaknesses are the abstract behavioral-guidelines section and the orphaned bundle script that is never referenced by its actual path.

Suggestions

Reference the real bundle file explicitly (e.g., 'See scripts/my-custom-skill.py for a working Pattern B example') so the provided script is discoverable from SKILL.md.

Make the behavioral guidelines concrete in the style of the journal example — specify what to ask_env for and what state shape to write — rather than 'query the environment for relevant information'.

Dimension	Reasoning	Score
Conciseness	The body is efficient and sectioned — the Pattern B details ('cached in-process module via entrypoint(argv, ctx)', 'dynamic wrapper/subprocess fallback') are system-specific knowledge Claude would not already have. Minor trimmable meta-lines ('This is a template for creating a custom agent skill') keep it below the 'every token earns its place' anchor.	4 / 5
Actionability	Guidance names concrete tools (`ask_env`, `read`/`write`/`append`, `finish`, `execute_skill_script`) and the journal example gives specific paths and an explicit instruction string. It falls short of fully copy-paste-ready because the behavioral guidelines remain abstract ('query the environment for relevant information') and the actual bundle script is never referenced by its real path.	4 / 5
Workflow Clarity	The journal example is a clear 4-step sequence (ask_env → read if exists → append → finish) with an explicit conditional ('load previous entries if it exists'). No validation checkpoints are present, but the operations are neither destructive nor batch, so the workflow-clarity cap at 3 does not apply; it is not a 5 because error-recovery/feedback steps are absent.	4 / 5
Progressive Disclosure	The ~45-line body is well organized into Pattern A/Pattern B, guidelines, and a worked example, and the skill is short enough not to need external references. However, the actual bundle file scripts/my-custom-skill.py exists but is only obliquely hinted at via the generic placeholder 'scripts/my-script.py', a minor navigation gap.	4 / 5
	Total	16 / 20 Passed

Description

25%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 placeholder: it names the concept (a custom-skill template) but states no concrete capabilities, no trigger conditions, and no distinguishing niche. It reads like scaffolding metadata rather than a functional skill description.

Suggestions

List the concrete capabilities of the skill (e.g., 'Scaffolds a new agent skill with frontmatter, behavioral guidelines, and an optional compute script') instead of the generic 'a template to get started'.

Add an explicit trigger clause, e.g., 'Use when creating a new custom agent skill or when the user asks to add, scaffold, or customize skills'.

Include natural trigger terms and synonyms users would actually say ('skill template', 'new skill', 'custom skill', 'agent skill') to improve both trigger quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	"Example custom skill — a template to get started" names the domain (custom skill template) but lists no concrete actions or capabilities, matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 1 because a domain is clearly named, and not a 3 because no concrete action verbs appear.	2 / 5
Completeness	"a template to get started" is a vague 'what' and there is no 'when'/'Use when...' clause at all, matching the anchor 'Has a vague what and no when'. The missing trigger guidance also caps completeness at 3, and the description sits below that.	2 / 5
Trigger Term Quality	The only keywords are "custom skill", "template", and "get started" — one or two generic terms with none of the natural phrases a user would say when needing this skill. It avoids a 1 because these are not pure technical jargon, but misses the relevant variations needed for a 3.	2 / 5
Distinctiveness Conflict Risk	"Example custom skill" is a placeholder-level label that would overlap with virtually any skill-creation or templating skill, matching 'Very broad; high overlap risk with many similar skills'. It is not a 3 because nothing in the description distinguishes it from other custom skills.	2 / 5
	Total	8 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: tsinghua-fib-lab/AgentSociety
Path: packages/agentsociety2/agentsociety2/custom/skills/examples/my-custom-skill/SKILL.md
Commit: 8cc5bb9

Reviewed: 6 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.