skill-share

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

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skill-share/SKILL.md

Quality

Content

46%Weight 40%Scale 1-5

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

The content is well-structured and reasonably concise but stops at describing capabilities instead of giving Claude executable steps, and the workflow lacks explicit validation checkpoints for its outward-facing Slack posting. Adding concrete code/commands and a validate-fix-retry loop would address the weakest dimensions.

Suggestions

Provide concrete, executable guidance: example Rube SLACK_SEND_MESSAGE / SLACK_POST_MESSAGE_WITH_BLOCKS call payloads, a SKILL.md frontmatter template, and the exact packaging command, instead of narrative descriptions.

Add an explicit validate-then-notify feedback loop (e.g., 'Run validation; if it fails, fix and re-validate; only post to Slack when validation passes') so the outward-facing posting step has a checkpoint.

Collapse the overlapping 'When to use', 'Key Features', and 'How It Works' sections and drop the awkward 'User says he wants...' line to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient bullet prose, but the 'When to use', 'Key Features', and 'How It Works' sections overlap, and phrases like 'Also use this skill when: User says he wants to create/share his skill' add padding.	3 / 5
Actionability	The body describes capabilities at a high level ('Creates properly structured skill directories', 'Packages the skill as a zip file') but provides no executable code, concrete commands, or worked Rube API call examples; the 'Example Usage' block is narrative rather than runnable.	2 / 5
Workflow Clarity	The five-step 'How It Works' sequence is clear and includes a validation step, but there is no explicit checkpoint or fix-and-retry feedback loop for the outward-facing Slack post or packaging, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The single ~80-line file is well-organized into clear sections with no nested references; the only minor gap is that it could point to separate templates or Rube API reference material rather than inlining everything.	4 / 5
	Total	12 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 clearly conveys what the skill does but omits any explicit trigger guidance, so it answers 'what' without 'when'. Trimming the buzzword tail and adding a 'Use when...' clause would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause stating concrete trigger phrases (e.g., 'Use when the user wants to create a Claude skill and share it with the team on Slack') to satisfy the completeness trigger requirement.

Replace 'for seamless team collaboration and skill discovery' with a concrete additional action (e.g., 'validates skill structure and posts a summary to a Slack channel') to raise specificity.

Include natural synonyms users would actually say (e.g., 'build a skill', 'announce a skill', 'Slack', '.zip') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('creates new Claude skills', 'automatically shares them on Slack'), but 'seamless team collaboration and skill discovery' is buzzword fluff rather than a concrete action, and coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clearly stated, but the 'when' is absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant keywords are present ('create Claude skills', 'share on Slack', 'Rube') but common variations, synonyms, and a natural 'Use when...' trigger phrase are missing.	3 / 5
Distinctiveness Conflict Risk	The combination of skill creation plus Slack sharing via Rube carves a mostly distinct niche with only minor overlap risk against a generic skill-creator skill.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/awesome-claude-skills
Path: skill-share/SKILL.md
Commit: be2a406

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