skill-share
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill skill-share40
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
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 a specific niche (creating Claude skills and sharing via Slack/Rube) but suffers from missing explicit trigger guidance and relies on vague marketing language ('seamless team collaboration'). It would benefit from concrete action verbs and a clear 'Use when...' clause to help Claude select this skill appropriately.
Suggestions
Add an explicit 'Use when...' clause with trigger phrases like 'create a skill', 'share skill on Slack', 'post to Rube', or 'make a new Claude skill'.
Replace vague phrases like 'seamless team collaboration and skill discovery' with concrete actions such as 'posts skill files to Slack channels' or 'notifies team members of new skills'.
Include natural user language variations like 'make a skill', 'new skill', 'share with team', 'Slack notification' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Claude skills, Slack sharing) and mentions actions ('creates new Claude skills', 'shares them on Slack'), but lacks specific details about what creating a skill entails or what Rube does beyond 'seamless team collaboration'. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no trigger guidance at all. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords ('Claude skills', 'Slack', 'Rube', 'team collaboration', 'skill discovery') but missing natural user phrases like 'make a skill', 'share skill', 'post to Slack', or 'create automation'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Claude skills' + 'Slack' + 'Rube' is fairly specific, but 'team collaboration' and 'skill discovery' are generic phrases that could overlap with other collaboration or skill-related tools. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is primarily descriptive marketing copy rather than actionable instructions. It explains what the skill does conceptually but provides no executable code, specific commands, or concrete implementation details. Claude would not be able to actually create skills or integrate with Slack based on this content alone.
Suggestions
Replace the 'Example Usage' prose with actual executable code showing how to create a skill directory structure and SKILL.md file
Add concrete Rube commands with exact syntax for SLACK_SEND_MESSAGE and other integrations, including example payloads
Remove the verbose 'When to use this skill' and 'Key Features' sections - replace with a quick start showing the actual workflow with real commands
Add validation checkpoint details: what specific errors to check for, how to handle failures, and retry logic
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive bullet lists explaining obvious concepts. The 'When to use this skill' section is redundant, and 'Key Features' describes rather than instructs. Much of this content explains what the skill does rather than how to use it. | 1 / 3 |
Actionability | No executable code, commands, or concrete implementation details. The 'Example Usage' section describes what happens conceptually but provides no actual commands or code to execute. References to scripts like 'skill creation scripts' are vague with no actual code provided. | 1 / 3 |
Workflow Clarity | The 'How It Works' section provides a numbered sequence (Initialization → Creation → Validation → Packaging → Slack Notification), but lacks any validation checkpoints, error handling, or concrete commands for each step. No feedback loops for when validation fails. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one file. No references to external documentation for Rube integration details, script implementations, or advanced configuration. The structure exists but content that should be separate (like Rube API details) is mentioned but not linked. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%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 | |
- 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.