CtrlK
BlogDocsLog inGet started
Tessl Logo

product-prioritization

Product strategy and feature prioritization — score features by user demand evidence, effort (human vs AI-assisted), strategic alignment, and market signal. Anti-sycophantic forcing questions to cut through opinion.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tightly organized, fully actionable instruction skill: concrete scoring formula, a non-negotiable forcing-question gate, and copy-paste output templates for three modes, with no padding of knowledge Claude already has. It is self-contained and well-structured without needing external bundle files.

DimensionReasoningScore

Conciseness

The body is lean and direct — principles, a forcing-question checklist, a scoring table, and compact output templates — without explaining concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor rather than the padded anchor 2.

3 / 3

Actionability

Provides a concrete scoring formula '(Demand × 3 + Impact × 2 + Alignment × 1) / Effort', explicit dimension definitions, a literal forcing-question checklist, and copy-paste-ready output templates for three modes, matching the 'fully executable... specific examples; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Three usage modes are clearly sequenced with numbered steps and an explicit forcing-question gate ('Do not skip them'); since these are analysis/recommendation flows rather than destructive or batch operations, the destructive-validation cap does not apply and the sequence matches the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is a single well-organized file (~140 lines) with clear sections; per the simple-skills note, well-organized content without external references scores 3, and the only references are one-level external project paths clearly signaled in the integration section.

3 / 3

Total

12

/

12

Passed

Description

67%

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 distinctive with concrete capability statements, but it omits an explicit 'Use when...' trigger clause, leaving the 'when to use' guidance implied rather than stated. Adding a natural-language trigger phrase would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause with natural user phrasings (e.g. 'Use when prioritizing a backlog, deciding what to build next, or ranking features by demand and effort').

Surface common trigger terms directly in the description (e.g. 'what should we build next', 'rank the backlog', 'is this worth building') rather than only in the activation block.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'score features by user demand evidence, effort (human vs AI-assisted), strategic alignment, and market signal' plus 'Anti-sycophantic forcing questions' — matching the 'lists multiple specific concrete actions' anchor rather than the partial anchor 2.

3 / 3

Completeness

The 'what' is strong (scoring framework, forcing questions, dimensions) but there is no explicit 'Use when...' trigger guidance in the description, which per the judging guidelines caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Contains relevant keywords like 'user demand' and 'market signal' but the description itself lacks natural user phrasings (e.g. 'Use when...') that live only in the activation block, so it has 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The 'Anti-sycophantic forcing questions' framing plus dual human/AI effort estimation carves a clear, distinctive niche unlikely to trigger the wrong skill, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nearai/ironclaw
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.