skill installer

Engineering Community

Skill notes

Commands

List installed skills: /skills Activate a skill: /skill <name> Scaffold a new skill: /skill new Install from GitHub: /skill install github:<owner>/<repo> Update installed skills: /skill update

Workflow

Identify the source: Existing local folder with SKILL.md GitHub repo or registry entry User request for a new skill scaffold Prefer DeepSeek's native /skill commands over ad hoc copying.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Hmbown · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Skill Installer

Use this skill when the user wants to find, install, update, trust, or remove a
DeepSeek skill.

## Commands

- List installed skills: `/skills`
- Activate a skill: `/skill <name>`
- Scaffold a new skill: `/skill new`
- Install from GitHub: `/skill install github:<owner>/<repo>`
- Update installed skills: `/skill update`
- Remove a skill: `/skill uninstall <name>`
- Trust a skill for script/tool use: `/skill trust <name>`

## Workflow

1. Identify the source:
   - Existing local folder with `SKILL.md`
   - GitHub repo or registry entry
   - User request for a new skill scaffold
2. Prefer DeepSeek's native `/skill` commands over ad hoc copying.
3. For GitHub/community skills, inspect the `SKILL.md` before recommending
   trust. Treat scripts and companion files as untrusted until reviewed.
4. After installing, tell the user to restart the session if the skill does not
   appear immediately in the available-skills list.
5. If a skill conflicts by name with a workspace skill, explain that workspace
   skill directories take precedence over global `~/.deepseek/skills`.

Do not execute community skill scripts unless the user explicitly asks and the
skill has been reviewed or trusted.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.