output-format-transformer
Skill0 starsChanged 7 months agoNo licenceView on GitHub
Transform synthesised research findings into a specific deliverable format with structural completeness enforced. Use when the user has synthesis output, research findings, or structured analysis and needs it formatted as a particular deliverable type. Triggers include: "turn this into a skill spec", "format as a system prompt", "make this into a framework", "create an implementation plan from this", "transform these findings", "formalise this as", "convert synthesis to", "structure this as", deliverable, output format, reformat findings. Do NOT use for: performing synthesis or analysis itself (→ source-quality-assessor, evidence-convergence-mapper), creating skills from requirements or conversation (→ skill-writer), writing research prompts from scratch without existing findings (→ deep-research-prompt-writer), collaborative long-form writing from scratch (→ content-research-writer), editing existing deliverables, or planning multi-pass research pipelines (→ research-orchestrator).
In this repository16 other files it gives its agents.
- brand-voiceSkill
- content-refinerSkill
- viral-hooksSkill
- archonSkill
- copy-style-qaSkill
- self-evaluation-rubricSkill
- skill-writerSkill
- content-research-writerSkill
- deep-research-prompt-writerSkill
- evidence-convergence-mapperSkill
- source-quality-assessorSkill
- high-stakes-responderSkill
- positioning-anglesSkill
- solo-founder-strategistSkill
- ux-docs-authorSkill
- ux-researcher-designerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 22 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈22
Distinctive · estimate
This author's own choices. Worth a look.
0
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 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
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.