- Home
- Skills
- Maxritter
- Pilot Shell
- Skill Sharing
skill-sharing_skill
- TypeScript
1.6k
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
1 month ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill maxritter/pilot-shell --skill skill-sharing- skill.md10.5 KB
Overview
This skill provides a concise reference and workflow guide for Skillshare (v0.17+) to share skills, extras (rules, commands, agents), and agents across machines and teams. It explains the two sharing modes (global vs project), extras management, cross-machine sync, and common CLI commands for non-interactive automation. Use it to set up team remotes, audit installs, and onboard new members with reproducible skill distribution.
How this skill works
Skillshare manages source directories (global: /.config/skillshare/skills or project: .skillshare/skills) and syncs them to target runtimes (/.claude/skills and extras targets). Extras are first-class resources with their own source root and targets and support merge, copy, or symlink sync modes. The Pilot Shell Console Share page and the skillshare CLI are the primary interfaces; non-interactive flags (--all, --json, --force) enable CI-friendly automation.
When to use it
- User says: “share”, “push”, “sync skills”, “skillshare”
- Set up cross-machine sharing or a Team Remote for organization-wide skills
- Manage extras (rules, commands, agents) across machines or projects
- Onboard a new team member with project/global skills and extras
- Run audits or health checks before CI or distribution
Best practices
- Prefer project-mode for repo-scoped skills and global-mode for personal multi-machine sync
- Always run skillshare sync after install/update/collect to propagate changes
- Use non-interactive flags (--all, --yes, --json, --force, --dry-run) for scripts and CI
- Keep Pilot-managed assets out of extras; use extras only for user-created resources
- Define prerequisites in a skill when non-standard tools are required
Example use cases
- Share a new skill repo with teammates: skillshare init --remote <git> && skillshare push
- Distribute rules across machines: skillshare extras init rules --target ~/.claude/rules && skillshare sync -g --all
- Onboard new developer in a project: clone repo, skillshare init -p, skillshare sync -p
- Audit and CI gate before merge: skillshare doctor --json and skillshare audit --threshold high
- Create a hub index for org discoverability: skillshare hub index --audit -o ./skillshare-hub.json
FAQ
Place a .skillignore at the source root or inside a tracked repo using gitignore syntax to exclude patterns; then run skillshare doctor to validate.
When should I use extras vs pilot-managed rules?
Use extras for user-created rules/commands/agents you want to sync across machines. Do not put Pilot-managed rules installed by the Pilot installer into extras; those are tracked by the installer manifest.