facct-related-work
Use when positioning an ACM FAccT submission across its many disciplinary lanes — algorithmic fairness/ML, HCI, law and policy, STS and critical theory, and prior FAccT/FAT* proceedings — writing delta-first contrast that a mixed reviewer pool will accept, citing borrowed constructs to their real origin, keeping self-citations mutually anonymous, and declaring overlap with workshops, preprints, and prior versions.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-related-work --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# FAccT Related Work Use this to audit novelty and disciplinary reach. FAccT reviewers come from **different fields**, and each expects to see the nearest work **in their lane** engaged. A fairness-metrics reviewer wants the ML fairness literature; a legal reviewer wants the relevant law and governance work; an STS/critical reviewer wants the theory you are (often implicitly) drawing on. The fastest way to lose a mixed panel is a bibliography that is deep in one field and blank in the others. Reopen the current CFP for anonymity, dual-submission, and prior-publication rules before advising. ## Positioning checks - **Name the FAccT novelty precisely.** What is new: a fairness/transparency method, an empirical harm nobody had measured, an accountability framework, a reframing of a taken-for-granted construct, a qualitative account of an affected community, or a legal-technical synthesis? - **Cover the disciplinary lanes** (see table). A paper that cites only its home field reads as unaware of the interdisciplinary conversation FAccT exists to host. - **Write delta-first.** Each closely related work gets one sentence naming what it did and one naming what you do differently — across t
- Positioning checks
- FAccT literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the facct-related-work skill do?
Use when positioning an ACM FAccT submission across its many disciplinary lanes — algorithmic fairness/ML, HCI, law and policy, STS and critical theory, and prior FAccT/FAT* proceedings — writing delta-first contrast that a mixed reviewer pool will accept, citing borrowed constructs to their real origin, keeping self-citations mutually anonymous, and declaring overlap with workshops, preprints, and prior versions.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-related-work --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.