CtrlK
BlogDocsLog inGet started
Tessl Logo

raffle-winner-picker

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

77

1.23x
Quality

Does it follow best practices?

Impact

99%

1.23x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is reasonably organized with concrete usage examples and clear workflows, but it is held back by redundant capability restatements, absent executable implementation detail, and no validation feedback loops in batch workflows. As a monolithic ~155-line file with no external references, its progressive disclosure is only moderate.

Suggestions

Provide the actual selection mechanism as executable code or a bundled script rather than only describing 'cryptographically random selection', so the guidance is copy-paste ready.

Add an explicit validation/checkpoint step in workflows (e.g., verify winner eligibility, confirm no duplicates, record timestamp for audit) with a retry loop, since winner selection is a batch operation.

Consolidate the repeated fairness/capability statements across 'What This Skill Does', 'Features', and 'Privacy & Fairness' into a single section to reduce redundancy and improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient and avoids explaining concepts Claude already knows, but capabilities are restated across 'What This Skill Does', 'Features', and 'Privacy & Fairness', so it could be tightened by removing redundant overlap.

2 / 3

Actionability

Provides concrete example prompts and a sample output, but the actual selection mechanism is only described ('Uses cryptographically random selection') rather than given as executable code or a script, leaving key implementation detail missing.

2 / 3

Workflow Clarity

Workflows are clearly sequenced (e.g., the 4-step Social Media Giveaway), but there are no validation checkpoints or feedback loops, and per the rubric missing validation for batch operations caps this at 2.

2 / 3

Progressive Disclosure

Content is well-organized into sections but is a monolithic single file with no bundle references; at ~155 lines, content such as the detailed output example and variant modes (weighted/exclusion/runner-up) could be split out for clearer navigation.

2 / 3

Total

8

/

12

Passed

Description

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.

A specific, well-targeted description in third person with good trigger-term coverage and a clear niche. Its main weakness is the absence of an explicit 'Use when...' clause, leaving the activation trigger implied rather than stated.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when picking random winners for giveaways, raffles, or contests from lists, spreadsheets, or Google Sheets') to fully satisfy the 'when' half of completeness.

Consider mentioning input formats like CSV/Excel/.xlsx explicitly in the description to strengthen trigger-term coverage for file-based use cases.

DimensionReasoningScore

Specificity

Names multiple concrete actions and sources ('Picks random winners from lists, spreadsheets, or Google Sheets', 'Ensures fair, unbiased selection'), matching the multiple-specific-actions anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Clearly states what the skill does, but the 'when' is only implied via 'for giveaways, raffles, and contests' with no explicit 'Use when...' trigger clause, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Covers natural terms users would say — 'giveaways, raffles, and contests', 'lists, spreadsheets, Google Sheets', 'random winners' — giving good keyword coverage rather than only a few relevant terms.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (winner picking for giveaways/raffles/contests from specific sources) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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
davepoon/buildwithclaude
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.