agentleFS
Tobi1chiTobi1chi/Skills-and-SmallTools/circuit-description-language/SKILL.md

circuit-description-language

Skill9 starsChanged 7 months agoNo licenceView on GitHub

Creates, explains, reviews, and converts human-readable text descriptions of circuits using CDL (Circuit Description Language). Use when the user wants to express circuit requirements or schematic information as CDL, decompose a circuit description into CDL blocks, review CDL syntax and completeness, convert CDL into a logical netlist, or generate the synchronized CSV BOM that mirrors the CDL component declarations. Also trigger on "describe this circuit", "write CDL", "convert CDL to netlist", "review my CDL", "check my circuit description", or when a schematic image needs a component-level text representation. This skill teaches CDL syntax and workflow only; it does not provide circuit design templates or prescribe how to implement specific modules. Do NOT trigger for parsing .enet files, product-level schematic design review, PCB layout, SPICE simulation, procurement, or EDA library mapping tasks.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

No licence file, so all rights are reserved — 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 364,980 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.