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

Content

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

This skill content reads like a marketing overview or README rather than actionable instructions for Claude. It describes what the skill does in abstract terms but provides zero executable code, no concrete commands, no templates, and no actual implementation guidance. The content is both verbose and empty of substance—it tells Claude about features without showing how to implement any of them.

Suggestions

Replace the 'Key Features' and 'When to use' sections with a concise 2-3 line summary, then provide actual executable code for creating skill directories, generating SKILL.md templates, and making Rube API calls.

Add concrete code examples for each step: directory creation (mkdir commands or Python script), SKILL.md template with actual YAML frontmatter, validation logic, zip packaging command, and actual Rube Slack API call with payload format.

Add explicit validation checkpoints with error handling: what does validation check, what errors can occur, and how to fix them before proceeding to packaging and Slack notification.

Include actual Rube API call examples with specific parameters (channel name, message format/blocks JSON) rather than just listing tool names like SLACK_SEND_MESSAGE.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive bullet-point lists that describe features rather than instruct. The 'Key Features' section, 'This skill is ideal for' section, and 'When to use this skill' section are all padded with redundant information Claude doesn't need. Much of the content restates the same ideas in different ways.	1 / 3
Actionability	No executable code, no concrete commands, no actual implementation details. The 'Example Usage' is a narrative description of what would happen, not actionable instructions. There are no actual scripts, no code snippets for creating skill directories, no Rube API call examples, and no templates for SKILL.md generation.	1 / 3
Workflow Clarity	The 5-step 'How It Works' section is a high-level description without any concrete commands, validation checkpoints, or error recovery steps. There's no guidance on what to do if validation fails, no actual validation commands, and no feedback loops for any of the steps.	1 / 3
Progressive Disclosure	No bundle files are provided despite references to scripts/, references/, and assets/ directories. There are no links to supporting files, no referenced paths, and the content is a monolithic description without any structured navigation to detailed implementation materials.	1 / 3
	Total	4 / 12 Passed

Description

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 provides a general sense of what the skill does but relies on vague language ('seamless team collaboration and skill discovery') and lacks explicit trigger guidance. It needs a 'Use when...' clause and more concrete action descriptions to help Claude reliably select this skill from a large pool.

Suggestions

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

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

Clarify what 'Rube' is (e.g., a Slack integration or bot) so Claude can better distinguish this skill from generic Slack-posting or skill-creation skills.

Dimension	Reasoning	Score
Specificity	It names the domain (creating Claude skills, sharing on Slack) and mentions some actions ('creates new Claude skills', 'shares them on Slack'), but lacks specific concrete actions like what creating a skill entails or what the sharing process involves.	2 / 3
Completeness	It describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also 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 skill', 'publish skill', 'share skill', 'skill.md', or 'post to Slack'. 'Seamless team collaboration and skill discovery' is vague fluff rather than useful trigger terms.	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-writing or file-creation skills. The Rube/Slack aspect adds some distinctiveness but isn't clearly delineated.	2 / 3
	Total	7 / 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: 8c53c59

Reviewed: 1 day 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.