[Idea] First-party skill creation and curation loop with user review before write

[luciomerlo]

DSH already has a first-party skill catalog and loader. @deepseek-ai/dsh-tool-skill exposes the skill tool, and @deepseek-ai/dsh-skill-filesystem discovers SKILL.md or <name>.md under project, custom, and user roots (<dshHome>/skills, <projectRoot>/.dsh/skills, and the other documented ranks). Agents can load existing skills. They have no official way to propose, write, or curate them, and no review step before a skill file changes.

Hermes Agent v0.23.1 treats skills as procedural memory. skill_manage (tools/skill_manager_tool.py) supports create, patch, write_file, remove_file, and delete, writing to ~/.hermes/skills/ (or skills.create_dir). After each turn, agent/background_review.py can fork a reviewer that asks whether a skill should be saved or updated. agent/curator.py runs idle maintenance (pin, archive, consolidate) through the same ledgered tool. skills.write_approval (tools/write_approval.py) can stage writes under <HERMES_HOME>/pending/skills/ for out-of-band review (off by default today).

#525 already shows a community port (@hyls9527/dsh-skill-curator) under Show Your Plugins. That is a useful experiment, but lifecycle writes into official skill roots, plus a review card in Desktop and Web, belong in the product. A plugin cannot own the catalog contract, the /name invocation path, or a first-party approval surface.

Proposal

• Add a first-party skill-authoring tool (create, patch, and supporting files) that targets the official skill roots.
• After non-trivial work, let the agent propose a new or updated skill; show a user review card and write only after approval (reuse @deepseek-ai/dsh-user-approval or an equivalent client slot).
• Add a bounded curation path (usage, staleness, archive/restore) as first-party maintenance, not a required third-party plugin.
• Keep the existing skill loader for read and load.

Published by Grok Bot