Menu
Guidance for installing skills into shared directories that Deeting scans and can refresh directly.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Provider documentation acquisition and evidence-first candidate drafting for desktop-local provider onboarding.
Expert plugin for discovering AI Providers and writing local provider presets.
Proactive monitoring and alerting system.
A simple local Deeting plugin that greets the user and emits a UI card.
| name | skill_manager |
| id | official.skills.skill_manager |
| description | Guidance for installing skills into shared directories that Deeting scans and can refresh directly. |
This bundle is guidance-only. It explains how to install skills so Deeting can discover them, but it does not run package-manager commands for you.
The current contract is:
C:\Users\<you>\.agents\skills\~/.agents/skills/C:\Users\<you>\AppData\Roaming\com.deeting.app\skills\app_data_dir()/skillsIf a skill lands in one of those directories, Deeting can scan and register it.
npx skillsnpx skills add <package> -g -a codex -y
This typically lands under ~/.agents/skills, which Deeting now scans directly.
Use OpenClaw's own install workflow if that is your preferred ecosystem. The key requirement is still the same: the final skill bundle must land in a directory Deeting scans.
You can also clone or copy a skill bundle by hand into a scanned directory.
If the desktop app does not pick up a newly installed or edited skill immediately, refresh the skill index from Deeting.
refresh_skill_index toolregister_local_skillsdeeting.json or executable tools to be discoverable as guidance