raffle-winner-picker
Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill raffle-winner-pickerOverall
score
69%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description with strong specificity and excellent trigger terms that users would naturally use. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The description clearly carves out a distinct niche for random winner selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to pick winners, run a raffle, select random entries, or conduct a fair drawing from a list.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Picks random winners', 'from lists, spreadsheets, or Google Sheets', 'for giveaways, raffles, and contests', and mentions 'fair, unbiased selection with transparency'. | 3 / 3 |
Completeness | Clearly answers 'what' (picks random winners from various sources for contests) but lacks an explicit 'Use when...' clause or equivalent trigger guidance to indicate when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'random winners', 'lists', 'spreadsheets', 'Google Sheets', 'giveaways', 'raffles', 'contests' - all common user vocabulary for this use case. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct triggers around random selection, winners, giveaways, raffles, and contests - unlikely to conflict with general spreadsheet or list processing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a good conceptual overview of raffle winner selection with clear use cases and example prompts, but lacks the concrete implementation details that would make it truly actionable. It's moderately verbose with sections explaining capabilities Claude would understand, and misses validation checkpoints for ensuring fair, verifiable selection processes.
Suggestions
Add executable Python code showing actual random selection implementation using secrets module or similar cryptographically secure method
Include validation steps in workflows: verify entry count matches expected, confirm no duplicate entries before selection, validate winner eligibility before announcement
Remove or condense the 'What This Skill Does' and 'Privacy & Fairness' sections - these explain concepts Claude already knows
Add concrete code for Google Sheets API access and CSV parsing rather than just showing prompt examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary sections like 'What This Skill Does' that explain obvious capabilities, and the 'Privacy & Fairness' section states things Claude would inherently understand. The feature lists and tips sections add bulk without proportional value. | 2 / 3 |
Actionability | Provides example prompts and expected output format, but lacks actual executable code for the random selection. The examples show what to ask Claude rather than concrete implementation details like which Python libraries to use or actual code snippets. | 2 / 3 |
Workflow Clarity | The 'Example Workflows' section provides clear sequences for different use cases, but lacks validation checkpoints. No verification steps for confirming data was loaded correctly or that selection was truly random before announcing winners. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear headers, but everything is in one file when some sections (like detailed workflows or weighted selection implementation) could be split out. No references to external documentation for advanced features. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.