CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rice

RICE feature prioritization with scoring and capacity planning. Usage: /rice prioritize <features.csv> [options]

60

Quality

76%

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

Quality

Content

88%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 efficient, actionable quick-start: concrete command syntax, a fully specified input format with example data, and a clearly signaled script pointer. Its only weaknesses are minor — no output-format documentation and references pointing outside the bundle — leaving little to trim and little ambiguity about what to do.

DimensionReasoningScore

Conciseness

The ~35-line body is lean: no concept explanations (it assumes Claude knows RICE), no padding, and each section (usage, input format, examples, script pointer) earns its place.

5 / 5

Actionability

Provides copy-paste-ready invocations, a concrete CSV schema with example rows, and a script with an inline argument spec, but never describes the output format and the referenced script path is not part of this bundle — minor gaps that keep it from fully executable/copy-paste complete.

4 / 5

Workflow Clarity

A simple single-purpose skill where the single action is unambiguous: run the prioritizer on a CSV whose format is fully specified. The operation is non-destructive, so the missing-validation cap for batch/destructive operations does not apply.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and clearly signaled one-level-deep references, but the script and SKILL.md paths are repo-relative ('product-team/skills/...') rather than bundle-relative, and no bundle files are actually present — a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

53%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 communicates a clear niche and concrete invocation syntax, but it entirely lacks a 'when to use' trigger clause and natural-language trigger phrases, so it functions more as a command reference than a discoverable skill description. It is specific about the domain yet thin on the breadth of actions performed.

Suggestions

Add a trigger clause, e.g. 'Use when prioritizing or ranking product features, creating a roadmap, or when the user mentions RICE, impact vs. effort, or capacity planning.'

Enumerate the concrete actions performed, e.g. 'Scores features on Reach, Impact, Confidence, Effort; ranks by RICE score; selects the optimal set under an effort capacity limit; outputs text, JSON, or CSV.'

Include natural synonyms users would actually say — 'rank features', 'score features', 'feature roadmap', 'prioritization framework' — to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('RICE feature prioritization') plus 1-2 concrete actions ('scoring and capacity planning'), but coverage is minimal — no ranking, output formats, or reporting actions, so it does not reach the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is clear (RICE feature prioritization with scoring and capacity planning), but there is no 'Use when...' or equivalent trigger clause — the 'Usage:' line documents invocation syntax, not when Claude should reach for the skill, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant keywords like 'RICE', 'feature prioritization', and 'capacity planning', but misses natural variations users would say such as 'rank features', 'score features', 'roadmap', or 'prioritization framework'.

3 / 5

Distinctiveness Conflict Risk

'RICE feature prioritization' is a clear niche unlikely to grab unrelated skills, but generic terms like 'scoring' and 'prioritization' leave minor overlap risk with other ranking or prioritization frameworks, keeping it below anchor 5.

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

alirezarezvani/claude-skills

Path

.gemini/skills/rice/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.