home-v1-skills-code-agent/skill-manager
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Restrict deploy targets to .agents and .claude skill dirs

Browse Source 
Remove $HOME/.cline/skills from the default deploy targets everywhere
(SKILL.md, deploy action, CLI help, Taskfiles), document what $HOME is
and how it is resolved, and restore the execute bit on the cli api
scripts (build.sh, scaffold.sh, validate.sh) so 'task build' works.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
oleg-lukasonok
2026-07-24 13:16:05 +03:00
co-authored by Claude Fable 5
parent 6042272ccc
commit bb184845b2
8 changed files with 18 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+9 -4
View File
@@ -8,7 +8,7 @@ description: >
procedure, or set of instructions into a portable skill that works across Claude Code,
GitHub Copilot, OpenAI Codex, and other compatible agents — or wants to deploy, install,
publish, or symlink any skill into the agent skill directories ($HOME/.agents/skills,
$HOME/.claude/skills, $HOME/.cline/skills), even if they just say "make this skill available".
$HOME/.claude/skills), even if they just say "make this skill available".
license: Proprietary
metadata:
author: workspace-swiss-knife
@@ -83,7 +83,7 @@ task scaffold -- --skill-name="my-skill" --output-dir="/path/to/.agents/skills"
# or directly via cli module:
task cli:scaffold -- --skill-name="my-skill" --output-dir="/path/to/.agents/skills"
# Deploy a skill into $HOME/.agents/skills, $HOME/.claude/skills and $HOME/.cline/skills
# Deploy a skill into $HOME/.agents/skills and $HOME/.claude/skills
task deploy -- --skill-dir="/absolute/path/to/skill"
# copy instead of symlink, replace existing real directories:
task deploy -- --skill-dir="/absolute/path/to/skill" --mode=copy --force
@@ -209,7 +209,12 @@ resolves to **absolute paths** and targets both canonical agent skill directorie
- `$HOME/.agents/skills/<skill-name>`
- `$HOME/.claude/skills/<skill-name>`
- `$HOME/.cline/skills/<skill-name>`
**About `$HOME`:** `$HOME` is the shell environment variable holding the current user's
home directory — e.g. `/Users/<username>` on macOS, `/home/<username>` on Linux. The
deploy action resolves it at runtime via Node's `os.homedir()`, so the same command works
for any user on any machine without hard-coding paths. `~` is the shell shorthand for the
same directory.
```bash
cd <skill-manager>/scripts
@@ -235,7 +240,7 @@ Rules:
- [ ] Scripts (if any) have `--help`, avoid interactive prompts, use structured output
- [ ] If `scripts/` exists: `scripts/.gitignore` is present (node_modules/, dist/, .env, .venv/)
- [ ] If `scripts/` exists: no source files (`.py`, `.ts`, `.js`, `.sh`) sit directly in `scripts/` — they must be in `scripts/src/` or `scripts/.scripts/`
- [ ] Skill is deployed (`task deploy`) so it resolves at `$HOME/.agents/skills/<name>`, `$HOME/.claude/skills/<name>` and `$HOME/.cline/skills/<name>` via absolute paths
- [ ] Skill is deployed (`task deploy`) so it resolves at `$HOME/.agents/skills/<name>` and `$HOME/.claude/skills/<name>` via absolute paths
## If the skill isn't triggering reliably