skills/backup/skill-deployer/SKILL.md
This skill deploys skills from the workspace's source code directory for skill development to the corresponding agent skills directory. You should use this skill when the user requests to deploy, install, or synchronize a skill. Or, when the skill has undergone code optimization, you should inquire with the user about using this skill for installation and deployment.
npx skillsauth add sampx/agent-tools skill-deployerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deploy AI agent skills from source to target directories.
# Deploy skill (copy mode)
python3 scripts/deploy-skill.py --source /path/to/my-skill --dest .agents/skills/
# Deploy with symlink (for development)
python3 scripts/deploy-skill.py --source /path/to/my-skill --dest .agents/skills/ --symlink
# List available skills in a directory
python3 scripts/list-skills.py --dir ~/my-skills
| Agent | Project Level | Global Level |
|-------|---------------|--------------|
| Universal | .agents/skills/ | - |
| Claude Code | .claude/skills/ | ~/.claude/skills/ |
| OpenCode | .opencode/skills/ | ~/.config/opencode/skills/ |
| Codex | - | ~/.codex/skills/ |
Deploy a skill from source to target directory.
python3 scripts/deploy-skill.py -s <source> -d <target> [options]
Options:
--source, -s - Source directory containing SKILL.md (required)--dest, -d - Target directory (required)--symlink, -l - Create symlink instead of copying--force, -f - Overwrite existing skill--name, -n - Custom skill name (defaults to source directory name)INBOX Auto-Move:
Skills deployed from INBOX/ are automatically moved to universal/ (sibling directory) after deployment, where universal/ stores accepted/installed universal skills. The version.json will record the new source path in universal.
List all skills in a directory.
python3 scripts/list-skills.py --dir <path> [--format json]
Skills can include a .skillignore file to exclude files from deployment (similar to .gitignore):
tests/
logs/
__pycache__/
*.pyc
Each deployed skill includes a version.json file for tracking:
{
"name": "skill-deployer",
"source_path": "projects/ontology/skills/my-skills/skill-deployer",
"content_hash": "a1b2c3d4...",
"deployed_at": "2026-02-28T14:15:00Z",
"deploy_type": "copy"
}
Fields:
name - Skill namesource_path - Source directory (relative to project root)content_hash - SHA256 hash of source contentsdeployed_at - Deployment timestamp (ISO 8601)deploy_type - copy or symlinkCheck which deployed skills have source updates:
# View sync status
python3 scripts/sync-skills.py
# Interactive update outdated skills
python3 scripts/sync-skills.py --update
# JSON output
python3 scripts/sync-skills.py --json
# Custom target directory
python3 scripts/sync-skills.py --dest ~/.claude/skills/
Options:
--dest, -d - Deployed skills directory (default: .agents/skills/)--json - Output in JSON format--update - Interactive update for outdated skillsSync States:
updated - Source has changed, needs redeploymentunchanged - No changes detectedorphaned - Deployed but source path no longer existsuntracked - No version.json (deployed before sync feature)--symlink during development for live updatestools
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
development
Workspace-level Git worktree management — create, list, remove, and prune isolated development environments. Use this skill whenever the user needs to create a worktree, set up an isolated workspace, work on multiple features in parallel, list existing worktrees, check what worktrees exist, remove or delete a worktree, clean up stale worktrees, or manage git working trees in any way. Triggers include "create worktree", "new worktree", "list worktrees", "show worktrees", "remove worktree", "delete worktree", "clean up worktree", "prune worktree", "isolated environment", "parallel development", "worktree for <project>", or any request involving git worktree operations.
development
Issue/Plan-driven development workflow. Tasks must be backed by a GitHub Issue or Plan. Trigger: issue references like #14, creating issues, creating plans, implementing plans, executing plans, checking plans, verifying plans, Plan lifecycle transitions (approve/complete/verify/archive), decomposing PRDs into Issues. Skip: spec-driven workflows, research/discussion/explanation only, small ad-hoc changes that don't need an Issue or Plan.
testing
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.