CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apm-4-check-tasks

Deliver a Task Prompt to an APM Worker. Use only when the User manually invokes this skill.

Quality

79%

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 ./templates/skills/apm-4-check-tasks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean orchestration skill: precise steps, concrete file paths, explicit fallback behavior for every failure mode, and appropriate delegation to the registration and task-execution guides. The only weakness is that the SKILL_PATH/GUIDE_PATH/VERSION template tokens are unresolved placeholders, which slightly reduces standalone executability.

DimensionReasoningScore

Conciseness

The ~12-line body is lean with zero padding and no explanation of concepts Claude already knows; even the densest sentence (step 1's registration handoff) is entirely operational. It clearly matches the 'every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete — the exact path `.apm/bus/<agent-slug>/task.md` plus explicit handling for each failure mode (unregistered, missing agent ID, no task waiting) — but `{SKILL_PATH:apm-3-initiate-worker}`, `{GUIDE_PATH:task-execution}`, and `{VERSION}` are unresolved template placeholders, a minor executability gap that keeps it just below the copy-paste-ready 5 anchor.

4 / 5

Workflow Clarity

A clear numbered sequence with role guards, a conditional entry path that hands off to the registration skill, and an explicit checkpoint in step 2 ("If no Task Prompt is waiting, say so and wait"); as a simple single-purpose skill with no destructive or batch operations, it fully meets the clarity anchor.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files to organize, and its two external pointers (`{SKILL_PATH:...}`, `{GUIDE_PATH:...}`) are one level deep and clearly signaled, so the simple-skill exception for a well-organized short body applies.

5 / 5

Total

19

/

20

Passed

Description

55%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 correctly covers the what/when pair with an explicit manual-invocation trigger, which is appropriate for a skill with model invocation disabled. Its weaknesses are jargon-heavy wording ("Task Prompt", "APM Worker") and the absence of natural user-facing trigger terms, leaving it comprehensible mainly to readers already inside the APM system.

Suggestions

Spell out what delivering a Task Prompt concretely involves (e.g., reading the worker's task file and executing it per the task-execution guide) so the 'what' is not pure jargon.

Add one or two natural trigger phrases users would actually say when invoking this skill manually, rather than relying solely on system jargon.

Briefly distinguish the Worker role from Planner/Manager in the description to reduce overlap with sibling apm-* skills.

DimensionReasoningScore

Specificity

"Deliver a Task Prompt to an APM Worker" names the domain and one concrete action, matching the 1-2-concrete-actions anchor; it is not purely generic like a 2, but does not list the several specific actions required for a 4.

3 / 5

Completeness

Both parts are present: what ("Deliver a Task Prompt to an APM Worker") and an explicit when ("Use only when the User manually invokes this skill"), satisfying the 'Use when' requirement so no cap at 3; it falls short of 5 because the 'what' is jargon-thin and no concrete trigger phrases beyond manual invocation are given.

4 / 5

Trigger Term Quality

The only terms are technical jargon ("Task Prompt", "APM Worker", "manually invokes this skill") with no natural phrases a user would say; this sits between the only-jargon anchor (1) and some-relevant-keywords anchor (3), but is noticeably thin on natural terms.

2 / 5

Distinctiveness Conflict Risk

Manual-only invocation (reinforced by disable-model-invocation) makes accidental triggering minimal and the APM Worker role carves a niche, but the description leans on jargon shared with sibling apm-* skills rather than clearly distinct triggers, so it does not fully reach the 5 anchor.

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

templates/skills/apm-4-check-tasks/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.