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 conveys the general purpose—creating Claude skills and sharing them on Slack—but relies on vague filler phrases like 'seamless team collaboration and skill discovery' instead of concrete actions. It critically lacks a 'Use when...' clause, making it hard for Claude to know when to select this skill, and the trigger terms don't cover natural user language variations.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'create a skill', 'new skill', 'share skill on Slack', 'post to Slack', 'publish skill'.

Replace vague phrases like 'seamless team collaboration and skill discovery' with specific actions such as 'generates SKILL.md files with proper YAML frontmatter and posts them to a designated Slack channel via Rube'.

Include file format references (e.g., 'SKILL.md', '.md') and common user phrasings to improve trigger term coverage.

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 Rube/Slack aspect adds some distinctiveness but isn't clearly scoped.	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 as a feature description or README rather than actionable instructions for Claude. It lacks any executable code, concrete commands, file templates, or specific API call formats. The content is verbose, repetitive, and entirely descriptive—telling Claude what the skill does rather than how to do it.

Suggestions

Replace the 'Key Features' marketing-style bullets with actual executable code: a Python script or shell commands for creating the skill directory structure, generating SKILL.md with YAML frontmatter, and packaging as zip.

Add concrete Rube API call examples showing exact message payloads for SLACK_SEND_MESSAGE and SLACK_POST_MESSAGE_WITH_BLOCKS, including the block format for rich skill announcements.

Add explicit validation steps with error handling: show what validation checks to run, what errors look like, and how to fix them before proceeding to packaging and Slack notification.

Provide a complete SKILL.md template with example YAML frontmatter so Claude knows exactly what metadata fields to generate and in what format.

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 'When to use this skill' section is padded with redundant trigger phrases. Much of this content tells Claude things it could infer or doesn't need.	1 / 3
Actionability	No executable code, no concrete commands, no actual file templates, no API call examples. The 'Example Usage' section describes what would happen in prose rather than providing actual commands or code. There are no copy-paste ready snippets for creating skill directories, generating YAML frontmatter, or sending Slack messages via Rube.	1 / 3
Workflow Clarity	The 5-step 'How It Works' sequence is vague and lacks any validation checkpoints, error handling, or feedback loops. Steps like 'Validation: Skill metadata is validated for correctness' give no indication of what to validate, how to validate, or what to do if validation fails. For a multi-step workflow involving file creation and external API calls, this is insufficient.	1 / 3
Progressive Disclosure	No bundle files are provided, yet the skill references scripts/, references/, and assets/ directories without any actual content. There are no links to supporting files, no referenced paths, and the content is a monolithic description with no clear navigation structure to deeper materials.	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: c911a92

Reviewed: 4 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.