agentleFS
LikeMindsCommunityLikeMindsCommunity/agentic-workflow-backend/.claude/skills/config-agent/SKILL.md

config-agent

Skill0 starsChanged 3 months agoLicence not identifiedView on GitHub

From a platform-specific Knowledge Base (KB) plus a Statement of Work / solution doc (SOW), generate the structured CONFIG the platform ingests — a JSON / XML / YAML / NodeFlow or any structured config file — strictly from the KB's grammar, verify it against the KB's own rules, and write it to the output directory (default fallback `outputs/<client>/generated/`). Nothing is executed. The skill is platform-agnostic: every schema, field name, node/event type, enum, naming rule, and definition of "valid" comes from the KB; the SOW (and any inline prompt) says only WHAT to build. Use when an operator points at a KB + SOW and wants the structured config the KB describes. Triggers: "generate the config / nodeflow from this KB + SOW", "build the {platform} config", "config-agent", "produce the {client} config from the KB and solution doc".

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.