facct-artifact-evaluation
Use when preparing the accountability artifacts that accompany an ACM FAccT paper — datasheets for datasets, model cards, data statements, audit and impact-assessment documentation, and released code/data — since FAccT's culture centers documentation and accountability infrastructure rather than a formal ACM artifact-badging track; covers what makes each genre credible, anonymized-review versus public-release versions, and consistency with the paper's harm claims.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-artifact-evaluation --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 Artifact Evaluation Use this for the material that backs a FAccT paper's transparency and accountability claims. Note the venue difference up front: FAccT does **not** run the SIGSOFT-style ACM Artifact Review and Badging track that software-engineering venues use, and it does not hand out Available/Functional/ Reusable/Reproduced badges. **待核实**: confirm on the current Author Guide whether any optional artifact/reproducibility appendix or badge scheme has been added for your cycle. What FAccT *does* have is a strong norm of **accountability documentation** — datasheets, model cards, data statements, audit trails, and impact assessments — plus released code and data. Treat those genres as your artifact and make each one credible on its own. ## The FAccT documentation genres (know which your paper needs) | Genre | What it documents | When your paper needs it | |---|---|---| | Datasheet for a dataset | Motivation, composition, collection, preprocessing, uses, distribution, maintenance | You release or rely on a dataset | | Model card | Intended use, training data, evaluation **disaggregated by group**, ethical considerations, limits | You release or audit a model | | Data sta
- The FAccT documentation genres (know which your paper needs)
- What a credible documentation artifact contains
- Released code and data (the reproducibility half)
- Anonymized review version vs. public release
- Consistency with the paper's harm claims
- Vignette: an audit paper's artifact set
- Calibration
- Output format
What does the facct-artifact-evaluation skill do?
Use when preparing the accountability artifacts that accompany an ACM FAccT paper — datasheets for datasets, model cards, data statements, audit and impact-assessment documentation, and released code/data — since FAccT's culture centers documentation and accountability infrastructure rather than a formal ACM artifact-badging track; covers what makes each genre credible, anonymized-review versus public-release versions, and consistency with the paper's harm claims.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-artifact-evaluation --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.