fluxly Search skills… ⌘K 中文 Publish

Skill Factory

Other Verified v1.0.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other · meta · automation · skills
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
100 / 100 · audit passed
Author / version / license
@amanning3390 · v1.0.0 · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python >=3.10
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Output preview skill-factory-amanning3390.preview 
---
name: Skill Factory
description: A meta-skill that silently watches your workflows and automatically generates reusable Hermes sk…
category: other
runtime: Python
---

# Skill Factory output preview

## PART A: Task fit
- Use case: A meta-skill that silently watches your workflows and automatically generates reusable Hermes skills from them. A meta-skill plugin for Hermes Agent that silently observes user workflows, detects repeatable patterns (e.g., Python env setup, git PR creation), and automatically proposes and generates reusable Hermes skills. Turns lived experience into proce….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “How It Works / Phase 1: Silent Observation / Phase 2: Trigger Conditions” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “A meta-skill that silently watches your workflows and automatically generates reusable Hermes skills from them. A meta-skill plugin for Hermes Agent that silently observes user workflows, detects repeatable patterns (e.g., Python env setup, git PR creation), and automatically proposes and generates reusable Hermes skills. Turns lived experience into proce…”.
- **02** When the source has headings, the agent prioritizes “How It Works / Phase 1: Silent Observation / Phase 2: Trigger Conditions” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: A meta-skill that silently watches your workflows and automatically generates reusable Hermes skills from them. A meta-skill plu…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “How It Works”, “Phase 1: Silent Observation”, “Phase 2: Trigger Conditions”, “Phase 3: Proposal & Generation”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name Skill Factory directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “How It Works / Phase 1: Silent Observation / Phase 2: Trigger Conditions” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

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