Obliteratus
RedWoodOG/Hermes-Desktop
Remove refusal behaviors from open-weight LLMs using OBLITERATUS — mechanistic interpretability techniques (diff-in-means, SVD, whitened SVD, LEACE, SAE decomposition, etc.) to excise guardrails…
A skill your agent uses when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject…
Install Facct Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-workflow --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-workflow .claude/skills/facct-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-workflow into .claude/skills/facct-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-workflow --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-workflow .agents/skills/facct-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-workflow into .agents/skills/facct-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-workflow --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-workflow .cursor/skills/facct-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-workflow into .cursor/skills/facct-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-workflow --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-workflow .gemini/skills/facct-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-workflow into .gemini/skills/facct-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/facct-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-workflow into .github/skills/facct-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/facct-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-workflow into .opencode/skills/facct-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 713 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject…
- Planning an ACM FAccT project timeline from venue fit through abstract registration
- SKILL.md covers Milestones (FAccT 2026…, Backward plan from the paper…, The single-deadline calendar… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- OpenReview submission
What it does
Facct Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject revise-and-resubmit round, two-round camera-ready, and in-person presentation, with backward-planning offsets for an interdisciplinary responsible-AI paper and honest handling of the single annual deadline.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering LLM guardrails. 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
- Planning an ACM FAccT project timeline from venue fit through abstract registration
- OpenReview submission
- The rebuttal window
- The new Accept/Revise/Reject revise-and-resubmit round
Example prompts
- “/facct-workflow”
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 Workflow loads about 1.5k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 713 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). 713 words, ~1,513 tokens.
Download SKILL.mdSave it as
.claude/skills/facct-workflow/SKILL.md (or your agent's skills folder).- name
- facct-workflow
- description
- Use when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject revise-and-resubmit round, two-round camera-ready, and in-person presentation, with backward-planning offsets for an interdisciplinary responsible-AI paper and honest handling of the single annual deadline.
FAccT Workflow
Use this as the project-management skill for a FAccT submission. Replace every date with the current official Important Dates page and work backwards from the abstract-registration deadline, which precedes the paper deadline and is a hard gate: miss it and OpenReview will not accept your PDF. FAccT runs a single annual research deadline, and — new for the 2026 edition — a genuine Revise-and-resubmit round sits inside the review cycle, so plan for a possible revision, not just an accept/reject.
FAccT is a conference with no standing editor-in-chief; leadership is the per-edition General Chairs and Program Chair (FAccT 2026: General Chairs Su Lin Blodgett and Zeerak Talat, PC Chair Michael Madaio, verified 2026-07-09). Chairs rotate yearly; re-check the committees page rather than carrying a name forward. Since 1 January 2026 all ACM proceedings are Open Access, so budget for the ACM Open / APC question early rather than at camera-ready.
Milestones (FAccT 2026 calendar as the worked example)
- Venue fit: confirm FAccT over a pure-ML/HCI/law venue and confirm the contribution is
fairness/accountability/transparency-first (
facct-topic-selection). - Abstract registration: submit real title, abstract, authors, and focus areas by the abstract deadline (FAccT 2026: 8 January 2026). This gate cannot be reopened.
- Paper submission: upload the anonymized acmart PDF with its endmatter statements (FAccT 2026: 13 January 2026).
- Preliminary reviews + rebuttal: reviews released (FAccT 2026: 20 February 2026); a short rebuttal window for factual corrections, not debate.
- First notification: Accept / Revise / Reject (FAccT 2026: 2 March 2026).
- Revision (if issued): address Area-Chair-prioritized concerns and resubmit by the revision deadline (FAccT 2026: 25 March 2026); re-reviewed before a final decision.
- Camera-ready: Round-1 accepts (FAccT 2026: 24 April 2026); Revise-and-resubmit accepts (FAccT 2026: 11 May 2026).
- Present: every accepted paper — archival or non-archival — is presented at the conference (FAccT 2026: Montréal, June 25-28, 2026).
Backward plan from the paper deadline
| Weeks out (heuristic) | Interdisciplinary-responsible-AI milestone |
|---|---|
| 10+ | Research/critical question fixed; affected populations and disciplinary lane named |
| 8 | Data collected / interviews done / legal-doctrinal analysis drafted; provenance and consent logged |
| 6 | Analysis complete; disaggregated results or qualitative codes done; limitations drafted alongside |
| 4 | Full draft in the acmart template; endmatter statements drafted (ethics, adverse impacts) |
| 3 | Internal mock review by a reader outside your discipline (the mixed-reviewer stress test) |
| 2 | Harm/limitations hardened; related-work delta across disciplines sharpened; page budget met |
| 1 | Anonymity sweep (strip positionality/acks); Generative AI Usage Statement written; focus areas set |
| 0 | Abstract registered by its earlier gate, then paper + endmatter on OpenReview |
These offsets are planning heuristics only — anchor every one to the current Important Dates page, never to a previous cycle.
Show full SKILL.md (289 more words)Show less
The single-deadline calendar reality
FAccT runs one annual research deadline. As of 2026-07-09 the FAccT 2026 edition has just concluded in Montréal, so the live next target is FAccT 2027 (dates/venue 待核实). Two planning consequences:
- Missing the annual deadline costs roughly a year at FAccT; if the work is time-sensitive, a sibling venue (AIES, a fairness-focused ML workshop, or a CHI/CSCW deadline) or the CRAFT track may have a nearer date — factor that into routing rather than idling.
- A Revise decision keeps you inside the same cycle (revision deadline weeks after notification), not a year later — but this revise-and-resubmit round is new for 2026, so confirm it still exists and re-read its exact timing before relying on it.
Failure modes by stage
- Missing the abstract-registration gate — the single most common fatal error; without a registered abstract and focus areas there is no paper slot at all.
- Leaving endmatter statements to the final night — a rushed Ethical Considerations or Adverse Impacts statement reads as an afterthought to reviewers who take reflexivity seriously.
- Skipping the cross-discipline mock review — forfeits the one chance to hear "a lawyer/social scientist will not accept this framing" from a friend instead of a reviewer.
- Treating a Revise as a guaranteed accept — the re-review is real; budget the short revision window like a deadline.
- Positionality/acknowledgement leak — placing an identity-revealing statement in the anonymous submission is an anonymity violation, not a virtue.
Coordination notes
- Assign one owner for the endmatter statements (ethics, adverse impacts, Generative AI Usage) and another for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF and, later, the rebuttal and revision response — the re-review quotes them and the response must map each reviewer concern to a change.
Output format
[Current stage] idea / evidence / writing / registration / submitted / rebuttal / revise / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <abstract gate / anonymity / endmatter statements / evidence / revision window / presentation>
[Owner map] <task -> person or role>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Facct Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| ObliteratusRedWoodOG/Hermes-Desktop | 177 | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Lemonade Router Builderamd/skills | 398 | — | ~4k | Automated safety check: Pass | MIT | |
| Wp Project Triagegambitph/Stackable | 350 | 4 repos | ~371 | Automated safety check: Pass | GPL-3.0 | |
| Aisafetyhotwuyoscar/AISafetyHot-Hub | 224 | — | ~774 | Automated safety check: Pass | Custom licence | |
| Persona Designkangarooking/system-prompt-skills | 205 | 1 repos | ~956 | Automated safety check: Pass | MIT |
Similar skills
Lemonade Router Builder
amd/skills
Turns a natural-language description of routing intent into a valid Lemonade collection.router policy JSON.
Wp Project Triage
gambitph/Stackable
A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…
Aisafetyhot
wuyoscar/AISafetyHot-Hub
Read AI Safety HOT daily digests, search recent AI safety research and incidents, and follow current hot topics.
Persona Design
kangarooking/system-prompt-skills
当需要为 AI 产品定义核心身份、角色声明和能力边界时调用此 skill。典型场景包括：设计新 AI 产品的 system prompt 首段、为不同场景创建差异化角色（如教学助手 vs 编程代理）、重新定义 AI 与用户的关系框架。
Execution Guardrails
mrtooher/fable-mode
Always-on operational guardrails, model-independent. An agent skill from mrtooher/fable-mode.
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…
Related
Categories
Questions about Facct Workflow
What does Facct Workflow do?
A skill your agent uses when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject…. Facct Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject revise-and-resubmit round, two-round camera-ready, and in-person presentation, with backward-planning offsets for an interdisciplinary responsible-AI paper and honest handling of the single annual deadline.
When should I use Facct Workflow?
Facct Workflow fits situations like: planning an ACM FAccT project timeline from venue fit through abstract registration; openReview submission; the rebuttal window; the new Accept/Revise/Reject revise-and-resubmit round.
How do I install Facct Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-workflow -a claude-code`. Or copy the skill folder (FAccT-Skills/skills/facct-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/facct-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Facct Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-workflow -a codex`. Or copy the skill folder (FAccT-Skills/skills/facct-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/facct-workflow in your project. Codex loads it when a task matches its description.
Can I use Facct Workflow 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-workflow -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-workflow, .gemini/skills/facct-workflow, .github/skills/facct-workflow and .opencode/skills/facct-workflow in your project.
What does Facct Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Facct Workflow is instructions for the agent only.
Does Facct Workflow 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 Workflow 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 Workflow use?
Facct Workflow 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 Workflow use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Workflow?
Skills that share tags, products or a category with Facct Workflow: Obliteratus (RedWoodOG/Hermes-Desktop, 177 stars), Lemonade Router Builder (amd/skills, 398 stars), Wp Project Triage (gambitph/Stackable, 350 stars) and Aisafetyhot (wuyoscar/AISafetyHot-Hub, 224 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Facct Workflow?
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.