thoughts-to-artifact
Skill0 starsChanged 6 months agoMITView on GitHub
Transform a user's raw thoughts, dictation, transcript, notes, brainstorm, or conversational explanation into a structured communication artifact while preserving meaning, examples, nuance, and recoverable detail. Use for articles, documentation, skills, READMEs, messages, briefs, posts, or similar outputs when the source structure is incidental and the output should organize ideas by meaning rather than original speaking order.
In this repository13 other files it gives its agents.
- change-consistencySkill
- engineer-agentic-aiSkill
- format-markdownSkill
- information-representation-designSkill
- living-artifactsSkill
- messaging-frameworkSkill
- python-testingSkill
- relevance-first-information-designSkill
- reviewable-branch-diffsSkill
- review-ready-codeSkill
- securitySkill
- software-designSkill
- swe-methodSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Treat the source as an information set, not as an outline that must be copied in order.
- Distinctive: line 18
Remove transcript noise, false starts, and redundant wording only when no distinct information is lost.
- Distinctive: line 19
Do not invent missing claims or silently resolve genuine ambiguity.
- Distinctive: line 23
Do not discard examples merely because a generalized rule can be extracted from them.
- Distinctive: line 35
Verify that important source information was not lost during compression or abstraction.
- Very specific: line 46
Use format-markdown additionally when the requested artifact is Markdown and Markdown-specific syntax or linking rules matter.
≈ “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
Thoughts to Artifact
Core Principle
Treat the source as an information set, not as an outline that must be copied in order.
Reorganize ideas around the structure that best serves the target artifact while preserving the information needed to reconstruct the user's intended meaning.
Preserve Information, Not Source Order
- Group statements about the same concept even when they appeared far apart in the source.
- Reorder material when conceptual grouping, causal order, or target-audience flow is clearer than dictation order.
- Remove transcript noise, false starts, and redundant wording only when no distinct information is lost.
- Do not invent missing claims or silently resolve genuine ambiguity.
Preserve Concrete Evidence
Do not discard examples merely because a generalized rule can be extracted from them.
A generalization is a lossy encoding of concrete cases: the rule often cannot reconstruct the original examples, while the examples still contain evidence for deriving or challenging the rule. Preserve examples that add boundary conditions, causal detail, intent, counterexamples, or diagnostic value.
Transformation Procedure
- Identify the target artifact and its audience/purpose.
- Extract distinct claims, examples, constraints, causal explanations, questions, and decisions from the source.
- Group semantically related material regardless of where it appeared in the source.
- Separate general rules from the concrete examples that support or qualify them.
- Choose the appropriate representation with
information-representation-design. - Apply
relevance-first-information-designto decide what belongs at the current layer versus a deeper linked layer. - Preserve unresolved ambiguity explicitly instead of filling it in.
- Verify that important source information was not lost during compression or abstraction.
Loss Check
Before finishing, ask:
- Which concrete examples disappeared from the output, and did they carry unique information?
- Which nuance, exception, uncertainty, motivation, or causal explanation was compressed away?
- Could the user recover the important original intent from the transformed artifact?
- Did source chronology survive only where chronology itself matters?
Use format-markdown additionally when the requested artifact is Markdown and Markdown-specific syntax or linking rules matter.
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.

