Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
Agent skill
Focs Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public…
Install Focs Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-artifact-evaluation --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/FOCS-Skills/skills/focs-artifact-evaluation .claude/skills/focs-artifact-evaluation && 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 "focs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-artifact-evaluation into .claude/skills/focs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-artifact-evaluation", 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/FOCS-Skills/skills/focs-artifact-evaluationType 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 focs-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-artifact-evaluation --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/FOCS-Skills/skills/focs-artifact-evaluation .agents/skills/focs-artifact-evaluation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "focs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-artifact-evaluation into .agents/skills/focs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-artifact-evaluation", 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 focs-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-artifact-evaluation --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/FOCS-Skills/skills/focs-artifact-evaluation .cursor/skills/focs-artifact-evaluation && 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 "focs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-artifact-evaluation into .cursor/skills/focs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-artifact-evaluation", 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 FOCS-Skills/skills/focs-artifact-evaluation--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 focs-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-artifact-evaluation --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/FOCS-Skills/skills/focs-artifact-evaluation .gemini/skills/focs-artifact-evaluation && 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 "focs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-artifact-evaluation into .gemini/skills/focs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-artifact-evaluation", 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 focs-artifact-evaluationInstalls 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 focs-artifact-evaluation -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/FOCS-Skills/skills/focs-artifact-evaluation .github/skills/focs-artifact-evaluation && 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 "focs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-artifact-evaluation into .github/skills/focs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-artifact-evaluation", 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 focs-artifact-evaluation -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 focs-artifact-evaluation --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/FOCS-Skills/skills/focs-artifact-evaluation .opencode/skills/focs-artifact-evaluation && 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 "focs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-artifact-evaluation into .opencode/skills/focs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-artifact-evaluation", 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
focs-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 767 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public…
- Works in 3 steps: At project start: decide which lemmas,… → At submission: repository tagged;… → At acceptance: execute the camera-ready…
- Plus proof certificates
- SKILL.md covers The FOCS evidence inventory, Packaging a certificate that…, Version ledger: keeping three… and What not to build, plus 3 more sections
- Calls git
What it does
Focs Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public arXiv/ECCC full version is the artifact of record, plus proof certificates, checker code, and the IEEE Xplore version's supporting role.
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.
It sits in Research & Science, covering Academic paper search. It works with arXiv. 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
- Plus proof certificates
- The IEEE Xplore versions supporting role
Example prompts
- “/focs-artifact-evaluation”
Requirements
- Python 3
- Docker
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- At project start: decide which lemmas, if any, will be computer-assisted;
- At submission: repository tagged; certificates packaged; full version
- At acceptance: execute the camera-ready double deliverable
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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Focs Artifact Evaluation loads about 1.6k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 767 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). 767 words, ~1,582 tokens.
Download SKILL.mdSave it as
.claude/skills/focs-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- focs-artifact-evaluation
- description
- Use when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public arXiv/ECCC full version is the artifact of record, plus proof certificates, checker code, and the IEEE Xplore version's supporting role.
FOCS Artifact Evaluation
There is no artifact-evaluation committee, badge system, or code-submission channel at FOCS — the 2026 CFP contains none of that machinery (checked 2026-07-08). What it does contain is an expectation with teeth: authors of accepted papers are expected to make full versions, with complete proofs, publicly available by the camera-ready deadline. Read that as the venue's actual artifact policy. The proceedings entry in IEEE Xplore is the citable announcement; the public full version is the object the community will actually consult, teach from, and check. Plan the evidence around that split from day one, not after acceptance.
The FOCS evidence inventory
| Object | Host | Audience | Obligation level |
|---|---|---|---|
| Full version with all proofs | arXiv (cs.DS/cs.CC/quant-ph...) or ECCC | Referees (they look, even under double-blind), then everyone | Expected by camera-ready; wise at submission time |
| Proceedings version | IEEE Xplore / IEEE CS Digital Library | Citation graph, indexing | Required deliverable of acceptance |
| Certificates for computed proof steps | Ancillary files beside the full version | Skeptics re-verifying a machine-checked lemma | Required whenever a proof leans on computation |
| Independent checker code | Same, plus a tagged repository | Same skeptics | Required with the certificate |
| Illustration/search code | Repository linked from the full version | Curious readers | Courtesy |
| Formalization (Lean/Rocq/Isabelle) | Repository + explicit coverage statement | Growing formal-methods audience | Optional; state honestly which theorems are formalized |
Packaging a certificate that strangers can trust
The trust chain for a computer-assisted step must survive your own infrastructure disappearing. A packaging recipe that does:
# Everything a verifier needs, content-addressed and self-describing
mkdir lemma47-certificate
cp check_lemma47.py configs.enum README-VERIFY.md lemma47-certificate/
sha256sum lemma47-certificate/* > lemma47-certificate/SHA256SUMS
git tag -a focs2026-submitted -m "state at FOCS submission"
# README-VERIFY.md states: input, claim certified, expected output,
# runtime (~90 s), and environment ("Python 3.12, stdlib only")Include the certificate directory with the arXiv upload as ancillary files so it shares the paper's persistence guarantees — a departmental URL in a proof is a dead link on the timescale over which FOCS papers stay relevant. If the certificate is huge (SAT traces can reach gigabytes), archive it with a DOI service and print the hash in the paper so the object stays pinned even if re-hosted.
Version ledger: keeping three documents honest
The submission, the public full version, and the proceedings version drift unless actively synchronized. Keep a ledger in the repository:
focs2026-submittedtag — exactly what HotCRP received.- Full-version updates — each with a changelog entry ("v2: fixed sign error
in Lemma 6.3; theorem statements unchanged"); statement changes are
breaking events that require flagging, not silent repair
(
focs-reproducibility). - Proceedings version — page-limited derivative; every omission points to the full version ("complete proof in the full version, Section 7").
Under double-blind, the full version may already be public under your names
at submission time; theory practice accepts this, but the submission must
still not self-identify (focs-submission).
Show full SKILL.md (356 more words)Show less
What not to build
Effort spent on ML-conference artifact rituals is effort taken from proofs.
At this venue, skip: Docker images for illustration scripts (a README and
a pinned interpreter version suffice for code carrying no proof weight);
anonymized artifact links inside the submission (there is no artifact
reviewer to follow them — certificates ride with the paper or its ancillary
files); interactive demos and websites (theory referees want the object,
not the experience); and any "artifact appendix" section formatted after
systems-conference templates. The single question that allocates effort
correctly: will a skeptical reader in ten years need this object to
believe the theorem? If yes, engineer it to survive ten years; if no, a
courtesy link is enough.
Formalization claims, calibrated
Mechanized proofs are appearing in the FOCS orbit, and miscalibrated claims
about them are a new failure mode. If you formalize, state coverage
precisely: "Theorem 1 and Lemmas 3.1–3.4 are verified in Lean 4 (commit
a3f9c2); the reduction in Section 6 is not formalized." A blanket "our
results are machine-verified" claim that a reviewer falsifies by opening the
repository costs more credibility than formalizing nothing.
Choosing the host: arXiv vs ECCC
Both satisfy the CFP's expectation; the choice is about audience and mechanics. arXiv offers subject-class reach beyond TCS, ancillary-file support, and version history readable by everyone; ECCC (the Electronic Colloquium on Computational Complexity) offers a complexity-native audience, lightweight community screening, and a numbering scheme the complexity literature cites natively. Complexity-central papers often post to both. Whichever you choose, pick the arXiv license deliberately — the minimal arXiv license keeps journal options maximally open, while CC licenses ease reuse; and remember the proceedings version will carry an IEEE copyright, so the full version is where your distribution freedom lives.
Planning sequence
- At project start: decide which lemmas, if any, will be computer-assisted; those need certificate engineering, not retrofitting.
- At submission: repository tagged; certificates packaged; full version ready to post (or already posted) on arXiv/ECCC.
- At acceptance: execute the camera-ready double deliverable
(
focs-camera-ready) and make the public record complete before the conference — the New York talk should point at a live, final full version.
© 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 FOCS-Skills/skills/focs-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Focs Artifact Evaluation 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 |
|---|---|---|---|---|---|---|
| Focs Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 19 repos | ~8.1k | Automated safety check: Notes | MIT |
Similar skills
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
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
Works with
Categories
Questions about Focs Artifact Evaluation
What does Focs Artifact Evaluation do?
A skill your agent uses when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public…. Focs Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public arXiv/ECCC full version is the artifact of record, plus proof certificates, checker code, and the IEEE Xplore version's supporting role.
When should I use Focs Artifact Evaluation?
Focs Artifact Evaluation fits situations like: plus proof certificates; the IEEE Xplore versions supporting role.
How do I install Focs Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-artifact-evaluation -a claude-code`. Or copy the skill folder (FOCS-Skills/skills/focs-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/focs-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Focs Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-artifact-evaluation -a codex`. Or copy the skill folder (FOCS-Skills/skills/focs-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/focs-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Focs Artifact Evaluation 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 focs-artifact-evaluation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/focs-artifact-evaluation, .gemini/skills/focs-artifact-evaluation, .github/skills/focs-artifact-evaluation and .opencode/skills/focs-artifact-evaluation in your project.
What does Focs Artifact Evaluation need to run?
Going by SKILL.md and its folder, Focs Artifact Evaluation needs the command-line tools its instructions call (git). Our summary lists: Python 3; Docker.
Does Focs Artifact Evaluation access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Focs Artifact Evaluation 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 Focs Artifact Evaluation use?
Focs Artifact Evaluation 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 Focs Artifact Evaluation use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Focs Artifact Evaluation?
Skills that share tags, products or a category with Focs Artifact Evaluation: Read arXiv Paper (karpathy/nanochat, 59k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Openalex Database (neflibata-feng/MyArxiv-Agent, 126 stars) and Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Focs Artifact Evaluation?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.