菜单
Use when formatting citations or bibliographies in a scientific document. Covers the four dominant styles (APA, Chicago author-date, IEEE, Vancouver), in-text citation patterns, and the pitfalls of each (page numbers, et al. thresholds, DOI inclusion, ordering of references).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Open and drive a REAL Chromium browser pane inside anu's tmux session. Use this whenever you need to actually SEE or interact with a web page — check a localhost dev preview after starting a dev server, verify a deploy looks right, read a docs/page that needs JavaScript, reproduce a UI bug, or fill out / click through a web form. Renders a real page (JS/CSS/Canvas/WebGL) via the kitty graphics protocol, in the same Chromium the human sees, so they watch your actions live. Drive it with the `browser` command or the browser_* MCP tools (open/navigate/screenshot/read/snapshot/eval/click/crop/type).
Generate a repo dossier as one fixed-template black-and-white HTML page in the anu atlas (~/.anu/atlas/<repo>): summary, component tree, dependency graph, choices made, divergences, open questions. Fans out reader agents via the Workflow tool; archives each run for diffing. Invoked by /map. Use when the user runs /map or asks to map, explain, or explore this repo as a dossier.
Understand a repository — a black-and-white, table-first Load-Bearing Ledger that ranks every file by structural importance and explains why. Personalized PageRank over the bash-call + python-import graph (utility-down-weighted, entry-point-seeded) is the rank; each row carries a reason vector (imported-by, churn/hotspot, ownership, entry-point, cycle) so no number is bare. Deterministic, reproducible, no LLM — the same parse→JSON→fixed-template→~/.anu/grok/<repo> pattern as scene/trail/git. Use when the user runs `grok` or asks to understand/see the shape of a repo, what files matter, what's load-bearing, what's linked most, or what to read first.
You back a chat as a persistent working agent. Do the turn's work in your terminal (it's shown live to the person); write only your concise final answer to $ANU_CHAT_REPLY, which they read as your reply.
Produce a live rendered artifact (a chart, a computation, a small notebook) that flows inline into your chat answer — when, and only when, running code or plotting would genuinely serve the answer. You decide; writing the file is the only signal.
Git for agents — the cockpit that composes the commit DAG (scene) with the commitments (trail) into ONE graph joined by commit SHA, rendered as four lenses — Evolution (the commit DAG carrying the why, with counterfactual edges = the road not taken), Research (the commitment/hypothesis map), Commitments (what governs each scope), Live (agents now). One surface, lenses not modes; the commit is the truth, the rest decorates it. Run `gfa` (provisional command) → ~/.anu/git/<repo>/index.html. Use when the user wants to see a project evolving WITH its decisions and roads-not-taken, runs `gfa`, or asks for the git-for-agents view.
| name | citation-formatting |
| description | Use when formatting citations or bibliographies in a scientific document. Covers the four dominant styles (APA, Chicago author-date, IEEE, Vancouver), in-text citation patterns, and the pitfalls of each (page numbers, et al. thresholds, DOI inclusion, ordering of references). |
Four styles cover most science writing:
| Style | Where used | In-text | Reference list order |
|---|---|---|---|
| APA 7 | Psychology, education, much of social science | Author-date: (Smith, 2023) | Alphabetical |
| Chicago author-date | Some humanities-adjacent science, biology variants | Author-date: (Smith 2023) (no comma) | Alphabetical |
| IEEE | Engineering, CS | Numbered: [1] | By order of first citation |
| Vancouver / AMA | Medicine, biomedical | Numbered: (1) or superscript¹ | By order of first citation |
When the journal isn't specified, default to APA 7 for social/life sciences, IEEE for engineering/CS, then adjust to journal style sheet on submission.
(Smith, 2023) or Smith (2023) showed...(Smith & Lee, 2023), always both names.(Smith et al., 2023), with et al. from the first citation, except where ambiguous.(Smith, 2023a, 2023b).(Smith, 2023, p. 47).(Lee, 2022; Smith, 2023).Journal article:
Smith, A. B., & Lee, C. (2023). Title of the article in sentence case.
Journal Name in Title Case, 47(3), 112–128. https://doi.org/10.xxxx/yyyy
Book:
Smith, A. B. (2023). Title of the book in sentence case. Publisher.
Chapter in edited book:
Smith, A. B. (2023). Chapter title. In C. Lee (Ed.), Book title (pp. 47–72).
Publisher.
Preprint:
Smith, A. B. (2023). Title of the preprint. arXiv. https://arxiv.org/abs/2301.xxxxx
In-text: [1], [2, 5], [3]–[7]. Cited in order of first appearance.
[1] A. B. Smith and C. Lee, "Title of paper," Journal Name, vol. 47, no. 3,
pp. 112–128, 2023, doi: 10.xxxx/yyyy.
Notes:
et al. threshold confusion. APA 7 uses et al. from the first citation when there are 3+ authors. (APA 6 said "first time, list all up to 5." Don't use APA 6 anymore.)https://doi.org/10.xxxx/yyyy, not doi: prefix.Smith, A. B. not Smith, Aadarsh B..For BibTeX users: use biblatex (modern) over natbib (legacy). Style is set with \usepackage[style=apa]{biblatex} or [style=ieee]. The biber backend handles unicode names correctly.
Related: [[imrad-structure]].