skill-share
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Overall
score
39%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill skill-shareActivation
33%The description identifies its core purpose (creating and sharing Claude skills via Slack/Rube) but suffers from missing explicit trigger guidance and relies on buzzwords like 'seamless team collaboration' without concrete specifics. The lack of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill from a large skill library.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'create a skill', 'new skill', 'share skill on Slack', 'post to Rube', or 'skill template'.
Replace vague phrases like 'seamless team collaboration and skill discovery' with concrete actions such as 'posts skill files to designated Slack channels' or 'generates SKILL.md files with proper frontmatter'.
Include natural keyword variations users might say: 'make a skill', 'write a skill', 'share with team', 'Rube integration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Claude skills, Slack sharing) and mentions actions (creates, shares), but lacks specific details about what 'creating skills' entails or what Rube does beyond 'seamless collaboration'. | 2 / 3 |
Completeness | Describes what it does (creates skills, shares on Slack) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'Claude skills', 'Slack', and 'Rube', but missing natural variations users might say like 'make a skill', 'new skill', 'share skill', 'post to Slack', or 'skill template'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Claude skills' + 'Slack' + 'Rube' provides some distinctiveness, but 'team collaboration' and 'skill discovery' are vague enough to potentially overlap with other collaboration or skill-related tools. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
20%This skill content is primarily descriptive rather than instructive, explaining what the skill does conceptually without providing actionable guidance. It suffers from significant verbosity, repeating similar information across multiple sections while lacking the concrete code examples, commands, and file paths that would make it executable. The workflow is outlined but missing critical validation and error recovery steps.
Suggestions
Replace the verbose bullet lists with a concise 2-3 line summary of when to use this skill
Add executable code examples showing actual script invocations (e.g., `python scripts/create_skill.py --name pdf-analyzer --description '...'`)
Include concrete Rube API calls with actual payloads for Slack integration
Add validation checkpoints with error handling guidance (e.g., 'If validation fails, check X and retry')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive bullet lists explaining concepts Claude already knows. The 'When to use this skill' section alone has 15+ bullet points that could be condensed to 2-3 lines. Repeats information across sections (e.g., skill creation features mentioned multiple times). | 1 / 3 |
Actionability | No executable code, commands, or concrete examples. The 'Example Usage' section describes what happens conceptually but provides no actual commands or code to run. No file paths, no script invocations, no API calls shown. | 1 / 3 |
Workflow Clarity | The 'How It Works' section provides a clear 5-step sequence, but lacks validation checkpoints, error handling, or feedback loops. No guidance on what to do if validation fails or Slack posting 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 locations, or advanced configuration. The skill mentions scripts/ and references/ directories but doesn't link to them. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
88%Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 14 / 16 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.