Design Audit Against Rams' Principles
thedotmack/claude-mem
Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.
A skill your agent uses when designing or auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines, qualitative and participatory studies with…
MITAuto-check passed
Install Facct Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-experiments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/FAccT-Skills/skills/facct-experiments .claude/skills/facct-experiments && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "facct-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-experiments into .claude/skills/facct-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-experiments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-experimentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-experiments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/FAccT-Skills/skills/facct-experiments .agents/skills/facct-experiments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "facct-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-experiments into .agents/skills/facct-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-experiments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-experiments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/FAccT-Skills/skills/facct-experiments .cursor/skills/facct-experiments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "facct-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-experiments into .cursor/skills/facct-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-experiments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path FAccT-Skills/skills/facct-experiments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-experiments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/FAccT-Skills/skills/facct-experiments .gemini/skills/facct-experiments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "facct-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-experiments into .gemini/skills/facct-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-experiments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-experimentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/FAccT-Skills/skills/facct-experiments .github/skills/facct-experiments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "facct-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-experiments into .github/skills/facct-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-experiments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-experiments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/FAccT-Skills/skills/facct-experiments .opencode/skills/facct-experiments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "facct-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-experiments into .opencode/skills/facct-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-experiments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
facct-experiments- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 653 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when designing or auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines, qualitative and participatory studies with…
- Auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines
- SKILL.md covers Evaluation audit, Claim-to-evidence design table, Handling protected attributes… and Mixed-methods and…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Qualitative and participatory studies with coding and reflexivity
What it does
Facct Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines, qualitative and participatory studies with coding and reflexivity, mixed-methods designs, sound handling of protected attributes and proxies, consent and IRB for human-subjects and community-facing work, and matching evidence to the shape of a fairness/accountability/transparency claim.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines
- Qualitative and participatory studies with coding and reflexivity
- Mixed-methods designs
- Sound handling of protected attributes and proxies
Example prompts
- “/facct-experiments”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Facct Experiments loads about 1.6k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 653 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 653 words, ~1,555 tokens.
Download SKILL.mdSave it as
.claude/skills/facct-experiments/SKILL.md (or your agent's skills folder).- name
- facct-experiments
- description
- Use when designing or auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines, qualitative and participatory studies with coding and reflexivity, mixed-methods designs, sound handling of protected attributes and proxies, consent and IRB for human-subjects and community-facing work, and matching evidence to the shape of a fairness/accountability/transparency claim.
FAccT Experiments
Use this before submission when the empirical story is not yet locked. FAccT evidence is not leaderboard evidence: the reviewer pool asks whether your study actually shows the harm, disparity, accountability gap, or transparency effect you claim, on the people you claim it for, with methods honest about their limits. The organizing principle is evidence proportional to the claim — and because FAccT is interdisciplinary, "evidence" can be a disaggregated statistical audit, a coded interview corpus, a participatory study, or a documented case, each held to its own field's standard of rigor.
Evaluation audit
- Match evidence to the claim shape. A claim about disparate harm needs disaggregated results by subgroup, not aggregate accuracy; a claim about how affected people experience a system needs qualitative or behavioral data from those people; a claim about accountability needs the institutional/process evidence, not a metric.
- Disaggregate, and defend the groups. Report metrics per protected/affected subgroup with uncertainty. State how group membership was defined and measured — proxies for race, gender, disability, or income carry construct-validity risk you must name and bound.
- Choose fair baselines and fair comparisons. For a fairness method, compare against the strongest prior fairness intervention and the do-nothing baseline, with an equal, documented budget; for an audit, compare against the vendor's own claims or a documented ground truth.
- Hold qualitative work to method. Coding schemes, inter-coder agreement where appropriate, saturation, an audit trail, and reflexivity about the researchers' standpoint — qualitative rigor is first-class at FAccT, not a soft option.
- Treat human subjects and communities with care. Document consent, IRB/ethics approval or its considered absence, compensation, data minimization, and how you avoid re-identifying or re-harming the people in your data — this is scored, and it feeds the Ethical Considerations statement.
- Design harms and limits in, not on. Know before you run which populations you cannot speak for and which disparities your instrument might miss, and instrument to surface them.
Claim-to-evidence design table
| FAccT claim | Matching evidence | Reject pattern avoided |
|---|---|---|
| "System X harms group G more" | Disaggregated error/outcome metrics by G, with CIs, on real data | "Aggregate accuracy hides the subgroup gap" |
| "Our method reduces the disparity" | Gap before/after vs. a tuned fairness baseline + the accuracy cost | "Fairness improved, utility cost never reported" |
| "Affected people cannot contest decisions" | Interviews/observation with those people, coded and reflexive | "Researcher speculation stands in for lived experience" |
| "This documentation improves transparency" | A study of whether real users act differently with it | "Assumed usefulness; never tested with a reader" |
| "The proxy is valid for the protected attribute" | Validation of the proxy against ground truth, error stated | "Proxy treated as truth; construct threat ignored" |
Show full SKILL.md (219 more words)Show less
Handling protected attributes and proxies
[Definition] state how each group is defined; whose categories are these, and who is erased by them?
[Measurement] is the attribute observed, self-reported, or inferred? report proxy error and bias
[Intersection] test intersectional subgroups where numbers allow; note where they are too small
[Consent] do the people classified know and agree? document the ethics basis
[Missingness] who is absent from the data entirely, and how does that bound the claim?Mixed-methods and participatory rigor
- Say why each method is present and what it does that the other cannot — triangulation, not decoration.
- For participatory or community-based work, document how the community shaped the questions, how findings return to them, and how power was handled — FAccT reviewers include people who do this seriously.
- Report negative and disconfirming evidence; a study that only confirms the authors' prior reads as advocacy, not research.
Vignette: auditing a hiring model
A paper claims a screening model disadvantages a protected group. The matching plan: obtain or construct a realistic labeled dataset with documented provenance; report selection/error rates disaggregated by group and intersection with confidence intervals; validate the group proxy and state its error; compare against the vendor's fairness claim; audit a sample of individual cases qualitatively for face validity; document the consent/ethics basis for using the data; and state plainly which populations the audit cannot speak to — every number traceable to a logged analysis in the supplementary material.
Statistical and methodological floor
- Uncertainty (CIs or equivalent) on every disaggregated comparison; multiple-comparison awareness across subgroups.
- For qualitative work: the coding scheme, agreement or a defense of a single-coder design, and the interview/observation protocol.
- The compute, data scale, and — for any human-subjects component — the sample and recruitment, not vague feasibility language.
Output format
[Evaluation readiness] strong / adequate / weak
[Claim -> evidence map] <claim: population / metric-or-method / uncertainty>
[Disaggregation] <groups reported? proxy validity stated? intersections where possible?>
[Ethics basis] <consent / IRB / compensation / re-harm avoidance documented? yes/no>
[Qual rigor] <coding / agreement / reflexivity present where relevant? yes/no>
[Decision-critical next run] <one study extension or analysis>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in FAccT-Skills/skills/facct-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Facct Experiments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Facct Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Design Audit Against Rams' Principlesthedotmack/claude-mem | 98k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep | 17k | 1 repos | ~2.7k | Automated safety check: Notes | MIT | |
| Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep | 17k | — | ~3.2k | Automated safety check: Notes | MIT | |
| Experiment Designeralirezarezvani/claude-skills | 28k | 1 repos | ~783 | Automated safety check: Pass | MIT | |
| OpenClaw Design Auditopenclaw/clawhub | 9.5k | — | ~498 | Automated safety check: Pass | MIT |
Similar skills
Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
Experiment Designer
alirezarezvani/claude-skills
A skill your agent uses when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.
OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
Design System
affaan-m/ECC
Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Facct Experiments
What does Facct Experiments do?
A skill your agent uses when designing or auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines, qualitative and participatory studies with…. Facct Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines, qualitative and participatory studies with coding and reflexivity, mixed-methods designs, sound handling of protected attributes and proxies, consent and IRB for human-subjects and community-facing work, and matching evidence to the shape of a fairness/accountability/transparency claim.
When should I use Facct Experiments?
Facct Experiments fits situations like: auditing ACM FAccT empirical work — quantitative fairness audits with disaggregated metrics and fair baselines; qualitative and participatory studies with coding and reflexivity; mixed-methods designs; sound handling of protected attributes and proxies.
How do I install Facct Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a claude-code`. Or copy the skill folder (FAccT-Skills/skills/facct-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/facct-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Facct Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a codex`. Or copy the skill folder (FAccT-Skills/skills/facct-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/facct-experiments in your project. Codex loads it when a task matches its description.
Can I use Facct Experiments in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-experiments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/facct-experiments, .gemini/skills/facct-experiments, .github/skills/facct-experiments and .opencode/skills/facct-experiments in your project.
What does Facct Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Facct Experiments is instructions for the agent only.
Does Facct Experiments access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Facct Experiments safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Facct Experiments use?
Facct Experiments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Facct Experiments use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Facct Experiments?
Skills that share tags, products or a category with Facct Experiments: Design Audit Against Rams' Principles (thedotmack/claude-mem, 98k stars), Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars) and Experiment Designer (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Facct Experiments?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.