Skill Factory

Other Community v1.0.0

Skill notes

Core Principle

"Every workflow you repeat is a skill waiting to be born." The Skill Factory turns lived experience into reusable procedural memory. It never interrupts. It watches. It proposes. It generates.

Phase 1: Silent Observation

While this skill is active, maintain a mental log of the following. Do NOT surface this log to the user — observe silently.

What to Track

Repeated actions: Any command, sequence, or approach used more than once Multi-step workflows: Sequences of 3+ steps that accomplish a coherent goal Tool combinations: Two or more tools used together in a consistent pattern Domain patterns: How the user approaches problems specific to their domain Fixes and workarounds: Recurring debugging patterns or solutions

What NOT to Track

One-off tasks with no clear reuse potential Trivial single-step actions (e.g., "read a file") Workflows already handled by existing Hermes skills Highly context-specific tasks that won't generalize

Phase 2: Trigger Conditions

Propose skill creation when ANY of the following occur: Trigger · Example User explicitly requests · "save this as a skill", "remember this workflow", "let's capture this" Slash command · /skill-factory propose Repeated pattern (2x+) · Same workflow appeared twice in the session

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
98 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Romanescu11 · v1.0.0 · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)
01
Phase 1: Silent Observation

While this skill is active, maintain a mental log of the following. Do NOT surface this log to the user — observe silently.

02
Phase 2: Trigger Conditions

Propose skill creation when ANY of the following occur: Trigger · Example User explicitly requests · "save this as a skill", "remember this workflow", "let's capture this" Slash command · `/skill-factory propose` Repeated pattern (2x+) · Same workflow appeared twice in the session

03
Phase 3: Proposal Format

When proposing a skill, output exactly this format: Only propose one skill at a time. If multiple patterns were detected, queue them and propose the most valuable one first.

04
Phase 4: Skill Generation

Phase 4: Skill Generation

05
Phase 5: Post-Generation

After successfully generating files: Confirm: `✅ Skill '[skill-name]' written to ~/.hermes/skills/[category]/[skill-name]/` Tell user: `Run 'hermes skills reload' to activate, or restart Hermes.` Ask: `I detected [N] other patterns this session. Want me to propose the next one?` Offer: `Want to review or edit the generated files before activating?`

Discussion

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