skill-share

A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

1.66x

Quality

16%

Does it follow best practices?

Impact

100%

1.66x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/skill-share/SKILL.md

Quality

Discovery

32%

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 identifies its core domain (creating Claude skills and sharing via Slack/Rube) but suffers from vague filler language ('seamless team collaboration and skill discovery') and lacks an explicit 'Use when...' clause. It needs more concrete action verbs and natural trigger terms to help Claude reliably select this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'create a new skill', 'share a skill on Slack', 'publish skill via Rube', 'make a skill.md'.

Replace vague phrases like 'seamless team collaboration and skill discovery' with specific actions such as 'generates skill.md files with YAML frontmatter, posts skill summaries to designated Slack channels via Rube'.

Include natural keyword variations users might say, such as 'new skill', 'write a skill', 'post to Slack', 'Rube integration', 'skill template'.

Dimension	Reasoning	Score
Specificity	Names the domain (creating Claude skills, sharing on Slack) and mentions some actions (creates, shares), but lacks specific concrete actions like 'writes YAML frontmatter', 'generates markdown content', 'posts to specific Slack channels'. The phrases 'seamless team collaboration and skill discovery' are vague fluff.	2 / 3
Completeness	Describes what it does (creates skills and shares on Slack) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and the 'what' portion is also somewhat weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'Claude skills', 'Slack', and 'Rube', but misses natural user phrases like 'make a new skill', 'share skill', 'post skill to Slack', 'skill.md', or 'publish skill'. 'Seamless team collaboration' is not something a user would naturally say.	2 / 3
Distinctiveness Conflict Risk	The combination of creating skills AND sharing on Slack via Rube is somewhat distinctive, but 'creates new Claude skills' could overlap with general skill-editing or skill-management skills. The Slack/Rube aspect adds some distinctiveness but isn't sharply delineated.	2 / 3
	Total	7 / 12 Passed

Implementation

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

This skill reads like a feature overview or README rather than actionable instructions for Claude. It describes what the skill does in abstract terms but never provides the concrete code, commands, templates, or API call formats needed to actually create skills or post to Slack via Rube. The content is simultaneously verbose (repeating the same concepts across multiple sections) and lacking in substance (no executable examples).

Suggestions

Replace the 'Key Features' marketing-style section with actual executable code: a SKILL.md template, directory creation commands, and concrete Rube API call examples (e.g., exact SLACK_SEND_MESSAGE payload format).

Add a concrete, copy-paste ready workflow with actual commands/code for each step, including validation checks and error recovery (e.g., 'If validation fails, check for missing frontmatter fields: name, description, version').

Remove the 'This skill is ideal for' and 'When to use this skill' padding — condense the trigger conditions to 2-3 bullet points maximum.

Provide actual Rube tool invocation examples with specific parameters, message formats, and expected responses rather than just listing tool names.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive bullet-point lists that describe features rather than instruct. The 'Key Features' section reads like marketing copy, and the 'This skill is ideal for' section is pure padding. Much of the content restates the same ideas in different ways.	1 / 3
Actionability	No executable code, no concrete commands, no actual API calls, no file templates, and no copy-paste ready content. The 'Example Usage' is a narrative description of what would happen rather than actual instructions Claude can follow. There are no actual Rube API call examples, no SKILL.md template content, no directory creation commands.	1 / 3
Workflow Clarity	The 5-step workflow (Initialization → Creation → Validation → Packaging → Slack Notification) is described at a high level but lacks any concrete implementation details, validation checkpoints, error handling, or feedback loops. There's no guidance on what to do if validation fails or if Slack posting fails.	1 / 3
Progressive Disclosure	Monolithic content with no references to external files, no bundle files provided, and no structured navigation. All content is inline but paradoxically lacks the actual detail needed. The skill references scripts and directories but provides no actual file content or references to supporting documentation.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: d065ead

Reviewed: 2 days 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.