CtrlK
BlogDocsLog inGet started
Tessl Logo

pm

Product Manager Nicolify v2. SSoT funcional vive en docs/product/ + docs/projects/. Director de orquesta — owner artefactos + orchestrator handoffs entre /po, /ux-{ui,agentico}, /architect, /dev-team, /auditor. Crea/cierra PIs, sprints, stories. Ratifica merges. Mantiene capability registry, INDEX, roadmap, modules.md. NO redacta specs (eso es /po). NO diseña arq (eso es /architect). Activa cuando user dice: '/pm', 'pm', 'product manager', 'feature nuevo', 'épica', 'PI nuevo', 'roadmap', 'qué tenemos', 'qué falta', 'priorizar', 'discovery', 'oportunidad', 'historia de usuario'.

62

Quality

73%

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

Quality

Content

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

Well-organized, action-oriented orchestration skill with a clear routing flow and validation gate, but it repeats content already in the description and fails to connect the rich reference bundle to the body, leaving valuable progressive-disclosure structure unused.

Suggestions

Link the relevant references/ files inline (e.g. point 'priorizar' at 06-rice-wsjf.md, 'discovery' at 01-opportunity-solution-tree.md, story-mapping at 02-user-story-mapping.md) so the bundle is discoverable one level deep.

De-duplicate the ownership / non-ownership lists between the description and the Rol section to trim tokens.

Add an explicit validate-step for the merge flow (e.g. re-read checkpoint after applying 07-merge.md) to lift workflow clarity toward a full feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but repeats ownership/non-ownership lists already implied by the description, and the routing ASCII diagram and capability-promotion steps add some length a competent reader could infer.

3 / 5

Actionability

Provides concrete executable guidance: exact file paths (docs/projects/active/PI-{N}/PI.md), a commands table mapping user phrases to actions, and a specific capability-promotion field-update recipe, with only minor gaps (templates referenced but not shown).

4 / 5

Workflow Clarity

Multi-step routing flow is clearly sequenced with explicit handoff order and a validation gate (06-audit/REVIEW-final.md APPROVED before 07-merge), though the destructive merge step relies on a referenced template rather than an inline validate-then-apply feedback loop.

4 / 5

Progressive Disclosure

The body references many internal docs paths and templates but never links the 10 provided bundle files in references/ (e.g. 04-prd-template.md, 06-rice-wsjf.md, 09-research-protocol.md); the actual reusable reference material is buried in the bundle and not surfaced from the SKILL body.

2 / 5

Total

13

/

20

Passed

Description

88%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 rich, concrete description that clearly states what the skill owns and when to activate it, with strong scoping against sibling skills. Slightly dense and could trim trigger redundancy, and 'feature nuevo'/'historia de usuario' may overlap with /po.

Suggestions

Trim redundant trigger enumeration and drop the leading '/pm' token so the list reads as natural user phrases only.

Disambiguate the 'feature nuevo' / 'historia de usuario' triggers from /po by noting PM decomposes stories while /po writes the spec.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (crea/cierra PIs, sprints, stories; ratifica merges; mantiene INDEX, roadmap, modules.md) plus explicit non-actions (NO redacta specs, NO diseña arq), giving comprehensive coverage of what the skill owns.

5 / 5

Completeness

Explicitly states both what it does (director de orquesta, owner de artefactos, handoffs) and when to activate it, via a concrete 'Activa cuando user dice:' trigger clause.

5 / 5

Trigger Term Quality

Covers many natural trigger phrases ('feature nuevo', 'épica', 'PI nuevo', 'roadmap', 'qué tenemos', 'qué falta', 'priorizar', 'historia de usuario'), but mixes in the command token '/pm' and a long enumeration; a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The skill defines a clear PM niche and explicitly scopes it against sibling skills (/po, /ux-*, /architect, /dev-team, /auditor), but the trigger 'feature nuevo'/'historia de usuario' could overlap with /po, leaving minor conflict risk.

4 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alpacapurpura/ap_sales_agent
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.