raffle-winner-picker

Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.

1.23x

Quality

57%

Does it follow best practices?

Impact

99%

1.23x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/raffle-winner-picker/SKILL.md

Quality

Content

53%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 content is well-structured and gives concrete invocation examples plus an output template, but it carries redundant use-case sections, lacks an executable selection mechanism, and omits explicit validation feedback loops for the batch winner-picking operation. It is a solid overview that would benefit from tightening and a verification step.

Suggestions

Merge the redundant 'When to Use This Skill' and 'Common Use Cases' sections, and consolidate 'What This Skill Does' with 'Features', to remove duplicated content.

Add an explicit validation/verification checkpoint in each workflow, e.g. 'Confirm no duplicate entries before selecting; if a winner is ineligible, re-pick from the remaining list.'

Provide a concrete selection mechanism (a script reference or a short code snippet using a cryptographically secure RNG) so the 'how' is executable rather than implied.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basics Claude already knows, but it duplicates content across 'When to Use This Skill' and 'Common Use Cases', and between 'What This Skill Does' and 'Features', so it could be tightened, matching the mostly-efficient-with-some-redundancy anchor.	3 / 5
Actionability	It provides concrete example prompts and a detailed output template, but gives no executable selection mechanism (no script, command, or code) and leaves the cryptographically-random method implicit, fitting the some-concrete-guidance-but-incomplete anchor.	3 / 5
Workflow Clarity	The numbered Example Workflows include a 'Verify winner details' step, but for a batch selection operation there is no explicit validate->fix->retry feedback loop or eligibility checkpoint inside the workflow, so per the batch-operation guidance it caps at 3.	3 / 5
Progressive Disclosure	The skill is a single, well-organized SKILL.md with clearly labeled sections and no bundle files; at ~100 lines it is over the simple-skill threshold but the structure is good with only minor organization gaps, matching the good-structure anchor.	4 / 5
	Total	13 / 20 Passed

Description

61%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 is third-person, on-domain, and rich in natural trigger terms, but it lacks an explicit 'Use when...' trigger clause and only names one core action, which caps completeness and specificity. It is distinct and unlikely to misfire, just not maximally explicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when running a giveaway, raffle, or contest and you need to pick fair, random winners from a list, spreadsheet, or Google Sheet.'

Expand the action list beyond 'picks winners' to concrete capabilities like 'pick one or multiple winners, exclude prior winners, and weight entries by ticket count'.

Include file-extension synonyms (CSV, .xlsx, Google Sheets) in the description to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (giveaways, raffles, contests) and a concrete action ('Picks random winners from lists, spreadsheets, or Google Sheets') plus a second quality claim ('Ensures fair, unbiased selection with transparency'), but it is essentially one core action rather than a comprehensive list, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	It has a clear 'what' (picks random winners from named sources) but no explicit 'Use when...' clause; the 'when' is only weakly implied via 'for giveaways, raffles, and contests', so per the missing-trigger-guidance cap it stays at 3.	3 / 5
Trigger Term Quality	Natural terms users would say are well covered ('random winners', 'giveaways', 'raffles', 'contests', 'spreadsheets', 'Google Sheets', 'lists'), missing only synonyms and file extensions like .csv or .xlsx, fitting the good-coverage anchor.	4 / 5
Distinctiveness Conflict Risk	The raffle/giveaway/contest niche is a clear, distinct trigger set with minimal conflict risk, with only minor overlap against generic random-list or survey-selection skills, matching the mostly-distinct anchor rather than the fully-distinct 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/raffle-winner-picker/SKILL.md
Commit: a9fa86d

Reviewed: about 19 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.