skill-share
- Repo stars 223
- License Complete terms in LICENSE.txt
- Author updated Live
- Author repo ordinary-claude-skills
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @Microck · Complete terms in LICENSE.txt
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python >=3.7
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-share
description: A skill that creates new Claude skills and automatically shares them on Slack using Rube for sea…
category: other
runtime: Python
---
# skill-share output preview
## PART A: Task fit
- Use case: A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery. Use this skill when you need to: Also use this skill when: This skill is ideal for: When you ask Claude to create a skill called "pdf-analyzer": This skill leverages Rube for: runs entirely locally; runs on Python >….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to use this skill / Key Features / 1. Skill Creation” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery. Use this skill when you need to: Also use this skill when: This skill is ideal for: When you ask Claude to create a skill called "pdf-analyzer": This skill leverages Rube for: runs entirely locally; runs on Python >…”.
- **02** When the source has headings, the agent prioritizes “When to use this skill / Key Features / 1. Skill Creation” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/skill-pdf-analyzer`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “When to use this skill / Key Features / 1. Skill Creation”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-share
description: A skill that creates new Claude skills and automatically shares them on Slack using Rube for sea…
category: other
source: Microck/ordinary-claude-skills
---
# skill-share
## When to use
- A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaborati…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to use this skill / Key Features / 1. Skill Creation” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-share" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to use this skill / Key Features / 1. Skill Creation
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} When to use this skill
Use this skill when you need to:
- Create new Claude skills with proper structure and metadata
- Generate skill packages ready for distribution
- Automatically share created skills on Slack channels for team visibility
- Validate skill structure before sharing
- Package and distribute skills to your team
Also use this skill when:
- User says he wants to create/share his skill
This skill is ideal for:
- Creating skills as part of team workflows
- Building internal tools that need skill creation + team notification
- Automating the skill development pipeline
- Collaborative skill creation with team notifications
Key Features
1. Skill Creation
- Creates properly structured skill directories with SKILL.md
- Generates standardized scripts/, references/, and assets/ directories
- Auto-generates YAML frontmatter with required metadata
- Enforces naming conventions (hyphen-case)
2. Skill Validation
- Validates SKILL.md format and required fields
- Checks naming conventions
- Ensures metadata completeness before packaging
3. Skill Packaging
- Creates distributable zip files
- Includes all skill assets and documentation
- Runs validation automatically before packaging
4. Slack Integration via Rube
- Automatically sends created skill information to designated Slack channels
- Shares skill metadata (name, description, link)
- Posts skill summary for team discovery
- Provides direct links to skill files
How It Works
- Initialization: Provide skill name and description
- Creation: Skill directory is created with proper structure
- Validation: Skill metadata is validated for correctness
- Packaging: Skill is packaged into a distributable format
- Slack Notification: Skill details are posted to your team's Slack channel
Example Usage
When you ask Claude to create a skill called "pdf-analyzer":
1. Creates /skill-pdf-analyzer/ with SKILL.md template
2. Generates structured directories (scripts/, references/, assets/)
3. Validates the skill structure
4. Packages the skill as a zip file
5. Posts to Slack: "New Skill Created: pdf-analyzer - Advanced PDF analysis and extraction capabilities"
Integration with Rube
This skill leverages Rube for:
- SLACK_SEND_MESSAGE: Posts skill information to team channels
- SLACK_POST_MESSAGE_WITH_BLOCKS: Shares rich formatted skill metadata
- SLACK_FIND_CHANNELS: Discovers target channels for skill announcements
Requirements
- Slack workspace connection via Rube
- Write access to skill creation directory
- Python 3.7+ for skill creation scripts
- Target Slack channel for skill notifications
Decide Fit First
Design Intent
How To Use It
Boundaries And Review