CtrlK
BlogDocsLog inGet started
Tessl Logo

apm-customization

Guides an AI agent through customizing APM templates, building releases, and managing a custom APM repository.

65

Quality

77%

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

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a lean, well-organized orientation with concrete commands and specific file references, and clean one-level navigation. Its main weakness is the absence of an explicit validation/retry feedback loop in the build-and-release workflow.

Suggestions

Add an explicit validation checkpoint in the release workflow (e.g. "If the test bundle fails, fix the templates and re-run build:release before tagging").

Include a quick verify step after "Update WORKFLOW.md first" to confirm runtime files still conform to STRUCTURE.md before proceeding.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, assumes Claude's competence, and avoids explaining basic concepts; each section (repository layout, placeholders, build, release) earns its place without padding, matching the 3-anchor.

3 / 3

Actionability

It gives concrete, executable commands ("npm install", "npm run build:release", "apm custom -r owner/repo") and specific file paths ("build/processors/placeholders.js", "build/build-config.json"), making the guidance copy-paste ready rather than abstract.

3 / 3

Workflow Clarity

Releasing and Making Changes provide numbered sequences with a test step, but there is no explicit validate->fix->retry feedback loop for the build/release pipeline; per the guidelines, missing validation checkpoints in batch/release operations caps this at 2.

2 / 3

Progressive Disclosure

The body is organized into clearly labeled sections with one-level-deep pointers to repository files (e.g. "Explore build/processors/placeholders.js") and no nested reference chains; navigation is straightforward.

3 / 3

Total

11

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 specific and distinct, naming concrete actions within a well-defined niche, but it omits an explicit "Use when..." trigger and relies on somewhat jargon-heavy terms, leaving the when-to-use guidance only implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when customizing APM templates, building releases, or managing a custom APM repository."

Surface natural user-facing phrasings (e.g. "forking APM", "apm custom", "template changes") alongside the existing terms.

DimensionReasoningScore

Specificity

"customizing APM templates, building releases, and managing a custom APM repository" lists multiple specific concrete actions, matching the 3-anchor of multiple distinct named actions rather than the 2-anchor of domain-plus-some-actions.

3 / 3

Completeness

It states clearly what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like "APM templates", "releases", and "repository" are domain-relevant but lean toward project jargon rather than the natural phrasings a user would say, and coverage lacks common variations; not the broad natural-term spread of the 3-anchor.

2 / 3

Distinctiveness Conflict Risk

The description carves a clear niche around APM template customization and release management with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
sdi2200262/agentic-project-management
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.