CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apm-customization

Guide changes to an APM source repository, including templates, builds and custom releases.

Quality

74%

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 ./skills/apm-customization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a lean, well-structured instruction skill: concrete commands and exact file paths, a clear five-phase workflow with approval and validation checkpoints, and efficient tables instead of prose. The only gaps are high-level release steps without specific commands and the absence of an explicit error-recovery feedback loop.

DimensionReasoningScore

Conciseness

The body is dense with zero padding — terse tables for the source layout and placeholders, and sentences like "A fork retains history for upstream merges. **Use this template** starts a repository with a clean history" — with no explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete, executable commands are present ("npm ci", "VERSION=1.1.0 npm run build:release", "apm custom -r owner/repo") plus exact paths ("build/processors/placeholders.js", "build/build-config.json"), but some steps remain high-level ("Create a new version tag and GitHub Release", "Adapt the repository's GitHub workflows"), fitting anchor 4 rather than fully copy-paste-ready coverage at 5.

4 / 5

Workflow Clarity

The five numbered sections give a clear sequence (layout → changes → build/check → release → documentation), the release is a numbered checklist starting with user approval, and the build step includes validation ("check paths, frontmatter, resolved placeholders and cross-references"), but there is no explicit validate-fix-retry feedback loop, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

The content is well-organized into clearly signaled sections with one-level-deep references (TERMINOLOGY.md, VERSIONING.md, SECURITY.md, the external customisation guide) and no nested or buried references; at ~65 lines with dense operational tables (placeholders, build targets) it slightly exceeds the simple-skill threshold where sections alone would merit a 5, fitting anchor 4 with only minor organization gaps.

4 / 5

Total

17

/

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 specific niche and concrete objects of change, but it omits any 'when to use' trigger clause and misses natural keyword variations such as 'fork' and 'customisation'. It is serviceable but reads more like a capability summary than an invocation trigger.

Suggestions

Add an explicit trigger clause, e.g. "Use when editing a fork or template of the APM repository, customising its templates, building a release, or publishing a custom version."

Include natural user phrasings and synonyms such as "fork", "customisation", and "APM release" to improve trigger-term coverage.

List the concrete actions performed (update standards and skills, build and validate ZIPs, tag and publish releases, document changes) instead of the generic "Guide changes".

DimensionReasoningScore

Specificity

"Guide changes to an APM source repository" names the domain, and "templates, builds and custom releases" are concrete objects, but the action verb is generic and coverage is not comprehensive — matching the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchor at 4.

3 / 5

Completeness

The 'what' is reasonably clear (guide changes to templates, builds and custom releases of the APM repository), but the description contains no 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Keywords like "APM", "templates", "builds" and "custom releases" are relevant, but common natural variations a user would say ("fork", "customisation", "release") are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than the good coverage at 4.

3 / 5

Distinctiveness Conflict Risk

"APM source repository" with "templates, builds and custom releases" carves a clear niche with only minor overlap risk against closely related repo-editing skills; it lacks the distinct trigger phrases of anchor 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

sdi2200262/agentic-project-management

Path

skills/apm-customization/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.