scad-intake
Skill26 starsChanged 5 months agoMITView on GitHub
Interpret a natural-language CAD request before geometry generation, identify materially different meanings, and return a bounded evidence-grounded brief or one high-information clarification question. Use before OpenSCAD generation when deterministic intake cannot confidently classify the request.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- developer-workflowSkill
- scad-chatSkill
- scad-codingSkill
- scad-generationSkill
- scad-improvementSkill
- scad-library-bosl2Skill
- scad-library-mcadSkill
- scad-library-nopscadlibSkill
- scad-library-policySkill
- scad-library-round-anythingSkill
- scad-library-threadsSkill
- scad-planningSkill
- scad-repairSkill
- scad-validation-reviewSkill
- scad-visual-validateSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Use AMBIGUOUS only when choosing the wrong interpretation would produce a substantially different CAD artifact.
- Very specific: line 19
Use MATCHED when one interpretation is sufficiently supported.
- Very specific: line 20
Use UNKNOWN when the request cannot support a useful interpretation.
- Distinctive: line 21
Never silently choose functional vs concept/display mode, internal cutaway vs exterior shell, printability, assembly motion, or component …
- Very specific: line 23
Keep assumptions empty unless an assumption is explicitly harmless, reversible, and exposed as an editable parameter.
≈ “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.
Files
SCAD Intake
Return exactly one JSON object. Do not write OpenSCAD and do not add Markdown.
Rules
- Preserve the user's language and explicit words.
- Distinguish materially different object types, uses, or modeling modes before generation.
- Use
AMBIGUOUSonly when choosing the wrong interpretation would produce a substantially different CAD artifact. Return 2–4 mutually exclusive options and one question that resolves the highest-impact uncertainty. - Use
MATCHEDwhen one interpretation is sufficiently supported. Missing numeric dimensions alone are not ambiguity when they can remain editable parameters. - Use
UNKNOWNwhen the request cannot support a useful interpretation. - Never silently choose functional vs concept/display mode, internal cutaway vs exterior shell, printability, assembly motion, or component count.
- Evidence strings must be exact substrings of the user request. Do not cite world knowledge as user evidence.
- Keep
assumptionsempty unless an assumption is explicitly harmless, reversible, and exposed as an editable parameter. Do not turn assumptions into user facts. - Acceptance criteria must describe observable geometry or explicit user constraints; do not claim that OpenSCAD, mesh, or visual validation has run.
- IDs must match
[a-z0-9][a-z0-9_-]*and remain stable descriptions, not random values.
Output
{
"status": "MATCHED|AMBIGUOUS|UNKNOWN",
"confidence": 0.0,
"concepts": [
{ "id": "concept_id", "label": "concept label", "evidence": ["exact request substring"] }
],
"interpretations": [
{
"id": "stable_interpretation_id",
"label": "user-facing interpretation",
"domain": "mechanical|architectural|product|concept|other",
"objectKind": "specific CAD object kind",
"probability": 0.0,
"evidence": ["exact request substring"],
"conflicts": []
}
],
"clarificationQuestion": "one question or null",
"assumptions": [],
"brief": {
"summary": "literal request summary",
"intendedUse": "explicit use or unknown",
"requiredFeatures": [],
"explicitConstraints": [],
"acceptanceCriteria": []
}
}For AMBIGUOUS, probabilities should sum to approximately 1 and clarificationQuestion must be non-empty. For MATCHED, put the most supported interpretation first and set clarificationQuestion to null. For UNKNOWN, return empty concepts/interpretations/assumptions and a brief containing only explicit facts.
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
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.

