CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-pm

Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.

Quality

80%

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 ./.agents/skills/oma-pm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured instruction-only skill body: an explicit scene-based workflow with validation, recovery, and exit criteria, plus unusually concrete guardrails specifying exact task fields and artifact paths. Its main gaps are minor: some duplicated/meta sections that could be trimmed, and reliance on external files (not present in this bundle) for the concrete task-schema example.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific operational detail (exact artifact paths, required task fields, pitfalls) and never explains concepts Claude already knows. Minor trimmable instances remain: the expected-outputs list is duplicated in prose and a YAML block, and the SSL-primitive Actions table adds abstract taxonomy with little operational value, so it fits 'Efficient; minor instances of over-explanation that could be trimmed' rather than the lean level of 5.

4 / 5

Actionability

Concrete, executable guidance dominates: guardrail 2 specifies exact task fields ("{id, description} acceptance criteria, covering required_checks with exact argv/cwd, a replayable task prompt, priority tier (1 = independent, lower runs first), dependencies"), the canonical path names the exact artifact ".agents/results/plan-{sessionId}.json", and pitfalls give concrete rewrites ("'Make it better' -> 'Add loading states to all forms'"). Not 5 because the actual plan/task JSON shape is delegated to resources/task-template.json rather than shown with an inline example, leaving a gap for the most common case.

4 / 5

Workflow Clarity

The Scenes sequence (PREPARE, REASON, ACT, VERIFY, FINALIZE) includes an explicit validation scene ("Check task atomicity, acceptance criteria, security/testing coverage, and dependency shape"), a Failure-and-recovery section with fix-and-retry guidance ("If acceptance criteria are vague, rewrite them into testable outcomes"), conditional Transitions, explicit Exit criteria, and a numbered guardrail checklist. This matches the top anchor: clear sequence with explicit validation steps, feedback loops for error recovery, and checklists for complex processes; the destructive-operation cap does not apply to a planning skill.

5 / 5

Progressive Disclosure

The body is an overview that pushes detail to one-level-deep, per-purpose-labeled references ("Plan examples: resources/examples.md", "Error recovery: resources/error-playbook.md", "Task schema: resources/task-template.json"), and keeps examples, ISO guidance, and playbooks out of the main file. It falls short of 5 because the flat References section mixes pure file pointers with inline behavioral directives (e.g., the human-readable tracker and API-contract destination rules) across ~13 ungrouped entries, which is 'Good structure... references mostly clear; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

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

A concise, third-person description that clearly states what the skill does and when to use it, with reasonably natural trigger terms. Its main weakness is that it compresses capabilities into a single action statement, leaving out task-breakdown vocabulary and common synonyms that would strengthen both trigger coverage and specificity.

Suggestions

Enumerate the concrete actions the skill performs, e.g., 'Turn product requirements into scoped tasks with dependencies, acceptance criteria, and API contracts' to lift specificity from one composite action to several specific ones.

Add common user phrasings to the trigger clause, such as 'Use when asked for implementation planning, task breakdown, roadmaps, or prioritization', to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Turn product requirements into scoped tasks with dependencies and acceptance criteria" names the domain (product requirements) and a single concrete action with its attributes, but does not list several distinct actions. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires multiple specific actions (e.g., extract/fill/merge).

3 / 5

Completeness

Both parts are explicitly answered: the 'what' is "Turn product requirements into scoped tasks with dependencies and acceptance criteria" and the 'when' is "Use for implementation planning and prioritization". Not 5 because the when-clause is brief with only two trigger terms, lacking the concrete multi-phrase trigger coverage of the top anchor; it has an explicit 'Use for...' clause so the missing-trigger cap of 3 does not apply.

4 / 5

Trigger Term Quality

Natural trigger phrases like "implementation planning", "prioritization", and "product requirements" are present and are phrases a user would plausibly say. Falls short of 5 because common variations such as "task breakdown", "roadmap", "spec", or "sprint planning" are missing, but coverage is better than the 'some relevant keywords' level of 3.

4 / 5

Distinctiveness Conflict Risk

The PM-planning niche (scoped tasks, dependencies, acceptance criteria) is mostly distinct from implementation or review skills, and "implementation planning and prioritization" gives clear triggers. Minor overlap risk remains with closely related task-management or orchestration-planning skills, so it fits 'Mostly distinct; minor overlap risk' rather than the minimal-conflict level of 5.

4 / 5

Total

15

/

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

first-fluke/oh-my-agent

Path

.agents/skills/oma-pm/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.