rice

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/rice/SKILL.md

Quality

Content

87%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, actionable overview for a single-purpose skill, with copy-paste commands and a clean reference to the supporting script. The only gap is the absence of validation/verification steps for the batch CSV operation, which caps workflow clarity at the midpoint.

Suggestions

Add a brief validation step before running the prioritizer, e.g. confirm the CSV header matches feature,reach,impact,confidence,effort and that numeric fields parse, so the batch operation is guarded.

Include a short note on how to sanity-check the ranked output (e.g. verify effort is non-zero) to introduce a feedback loop into the batch workflow.

Optionally show one concrete ranked-output snippet so the expected result of the command is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient, providing only usage, input format, examples, and a script reference without explaining what RICE is or other concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Provides copy-paste-ready invocations (/rice prioritize <features.csv> --capacity 20), a concrete CSV input schema, worked examples, and the exact script path with full argument syntax, covering the common cases.	5 / 5
Workflow Clarity	Although the single prioritization step is unambiguous, this is a batch operation over a CSV of features and the body includes no validation or verification steps (e.g. confirming CSV schema or sanity-checking scores), which caps workflow clarity at 3 per the batch-operation guideline.	3 / 5
Progressive Disclosure	Under 50 lines with no bundle files needed, organized into clear sections (Usage, Input Format, Examples, Scripts, Skill Reference), and the single external script reference is one level deep and clearly signaled, meeting the simple-skill exception for a top score.	5 / 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 clearly identifies a distinct, concrete niche (RICE prioritization with capacity planning) but lacks an explicit "Use when..." trigger clause and natural user phrasing, capping completeness and trigger-term quality at the midpoint. Adding trigger guidance and synonyms would meaningfully raise the score.

Suggestions

Add an explicit trigger clause such as "Use when the user wants to prioritize or rank product features, or asks about RICE scoring."

Include natural synonyms a user would actually say, e.g. "feature ranking", "prioritize roadmap items", or "score features by reach, impact, confidence, effort".

Expand the "what" beyond the two named actions (scoring, capacity planning) to list a third concrete capability such as ranking or export formats for stronger specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (RICE) and two concrete actions ("scoring" and "capacity planning"), matching the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage.	3 / 5
Completeness	Has a clear "what" (RICE prioritization with scoring and capacity planning) but provides only a Usage syntax line rather than an explicit "Use when..." trigger clause, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Contains relevant domain keywords ("RICE feature prioritization", "scoring", "capacity planning") but is missing natural phrases a user would say (e.g. "prioritize features", "score features") and common synonyms, matching the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"RICE feature prioritization" is a clearly distinct niche with minimal overlap risk against other skills, matching the "mostly distinct; minor overlap risk" anchor without reaching 5 because no explicit trigger phrases are provided.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 19392f7

Reviewed: ~14 hours ago

Table of Contents

Discovery Implementation Validation

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.