Agent skill
install-scripts
Install plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded
Install this agent skill to your Project
npx add-skill https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/install-scripts
SKILL.md
Install Scripts
Trigger
- Keywords: install scripts, setup scripts, copy scripts, install-scripts
When NOT to Use
- Installing rules (use
/install-rules) - Installing hooks (use
/install-hooks) - Full project setup (use
/project-setup)
Workflow
Phase 1: Locate plugin scripts dir
Phase 2: Enumerate scripts (core + skill scripts)
Phase 3: Determine install set (--all, --skill, specific names)
Phase 4: Copy scripts + dependencies to .claude/scripts/
Phase 4.5: Update manifest
Phase 5: Output report
Arguments
$ARGUMENTS
| Argument | Description |
|---|---|
--all |
Install all available core scripts |
--list |
List available core scripts without installing |
--dry-run |
Show what would be installed, no changes |
--force |
Overwrite existing scripts with different content |
--skill <name> |
Install all scripts from the specified skill |
--skill-all |
Install scripts from all skills |
--skill-list |
List all available skill scripts |
script-names... |
Specific scripts to install |
Script Types
| Type | Source | Target |
|---|---|---|
| Core scripts | scripts/*.js, scripts/*.sh |
.claude/scripts/ |
| Core lib | scripts/lib/*.js |
.claude/scripts/lib/ |
| Skill scripts | skills/<name>/scripts/* |
.claude/scripts/ |
Conflict Handling
| Scenario | Action |
|---|---|
| Target missing | Copy |
| Target identical | Skip (up to date) |
| Target differs | Skip + warn (use --force to overwrite) |
Output
## Install Scripts Report
| Script | Type | Status |
|--------|------|--------|
| precommit-runner.js | core | installed |
| lib/utils.js | core-lib | up to date |
| git-profile.sh | skill | installed |
Installed: N | Skipped: M | Conflicts: K
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
ask
Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.
project-brief
Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value.
codex-test-gen
Generate unit tests for specified functions using Codex MCP
bug-fix
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.
skill-health-check
Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
Didn't find tool you were looking for?