form-analysis
Skill1 starsChanged 45 days agoNo licenceView on GitHub
Analyze and visualize quantitative UX/product research data from surveys, spreadsheets, CSV/XLSX exports, or prepared analysis artifacts. Use when Codex needs to calculate or explain survey results, validate hypotheses, compare segments, handle single choice / multiple choice / scale questions, produce methodology notes, executive summaries, research reports, product implications, or reusable analysis plans for quantitative studies.
- Installs packages
In this repository9 other files it gives its agents.
- competitor-researchSkill
- figma-landingSkill
- first-screenSkill
- form-createSkill
- freelance-responseSkill
- interview-analysisSkill
- interview-guideSkill
- jtbdSkill
- site-auditSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
2
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.
Reviews can't be read right now.
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.