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
Stoc Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is…
Install Stoc Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-artifact-evaluation .claude/skills/stoc-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 "stoc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-artifact-evaluation into .claude/skills/stoc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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/STOC-Skills/skills/stoc-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 stoc-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-artifact-evaluation .agents/skills/stoc-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 "stoc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-artifact-evaluation into .agents/skills/stoc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-artifact-evaluation .cursor/skills/stoc-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 "stoc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-artifact-evaluation into .cursor/skills/stoc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 STOC-Skills/skills/stoc-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 stoc-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-artifact-evaluation .gemini/skills/stoc-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 "stoc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-artifact-evaluation into .gemini/skills/stoc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-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 stoc-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/STOC-Skills/skills/stoc-artifact-evaluation .github/skills/stoc-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 "stoc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-artifact-evaluation into .github/skills/stoc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-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 stoc-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/STOC-Skills/skills/stoc-artifact-evaluation .opencode/skills/stoc-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 "stoc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-artifact-evaluation into .opencode/skills/stoc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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
stoc-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 853 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is…
- Deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship
- SKILL.md covers The STOC evidence stack, When computation is inside the…, The full version as the… and Worked vignette: a…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC
What it does
Stoc Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC, plus verifiable certificates whenever a proof leans on computation, and optional mechanization.
Its SKILL.md is about 1.7k 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
- Deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship
- Given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC
- Plus verifiable certificates whenever a proof leans on computation
- Optional mechanization
Example prompts
- “/stoc-artifact-evaluation”
Requirements
- Python 3
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 (its code samples are bash).
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
Stoc Artifact Evaluation loads about 1.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 853 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). 853 words, ~1,741 tokens.
Download SKILL.mdSave it as
.claude/skills/stoc-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- stoc-artifact-evaluation
- description
- Use when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC, plus verifiable certificates whenever a proof leans on computation, and optional mechanization.
STOC Artifact Evaluation
STOC has no artifact-evaluation committee, no badges, and no code-upload channel: nothing of that kind appears in the STOC 2026 Call for Papers (checked 2026-07-08). Importing an ML-conference artifact checklist would answer questions this venue never asks. But STOC is not artifact-free either — the 2026 CFP expects accepted authors to place the full paper, with all proofs, on arXiv or ECCC by camera-ready. So the venue's real artifact policy is: the extended abstract advertises; the public full version is the object of record. Plan your evidence around that split.
The STOC evidence stack
| Evidence object | Lives where | Consumed by | Binding? |
|---|---|---|---|
| Theorem statements + overview | First 12 pages of the submission | The whole PC, guaranteed | Yes — the reading contract |
| Complete proofs | Appendix of the submission; later the arXiv/ECCC full version | Assigned reviewers; posterity | Yes — correctness rests here |
| Certificates for computer-assisted steps | Appendix description + released checker | Any skeptic with a laptop | Yes, if a proof step depends on them |
| Illustration code (plots, small searches) | Public repository linked from the full version | Casual readers | No |
| Mechanized proofs (Lean, Coq, Isabelle) | Repository + a coverage statement in the paper | Formal-methods-inclined readers | No, but rising in credibility value |
When computation is inside the proof
The one place STOC treats code with journal-referee seriousness is a computer-assisted step: an exhaustive case check, a SAT/ILP-certified combinatorial fact, an interval-arithmetic bound, a verified base case for an induction. House expectations, drawn from how such papers are read:
- State in the theorem's proof, not a footnote, that a step is machine-checked, and characterize the computation: search space, pruning logic, runtime, and what exactly the program's output certifies.
- Prefer computations that emit a certificate checkable by independent code (a DRAT proof from a SAT solver, an explicit combinatorial witness) over "our program found no counterexample."
- Ship the checker with the full version. arXiv accepts ancillary files, which is the cleanest venue-native mechanism:
# arXiv ancillary files ride inside the source tarball under anc/
mkdir -p anc
cp verify_certificate.py certificate.drat anc/
tar czf stoc-full.tar.gz full-version.tex macros.tex refs.bib anc/
# arXiv lists anc/* as downloadable ancillary files next to the paper- Pin the environment in one line ("Python 3.12, no dependencies; verified independently with drat-trim") — a skeptic should reproduce the check in minutes, because at least one will try.
The full version as the artifact of record
Before camera-ready (and ideally before submission, since theory reviewers routinely search for the full version even under double-blind), audit it as you would a released artifact:
- Completeness: no proof step deferred to "the full version" inside the full version; that document is the end of the chain.
- Self-containment: definitions and notation resolve internally; a reader must not need the extended abstract open in a second window.
- Versioning: arXiv revisions are the community's errata mechanism. When a bug is found post-publication, the corrected arXiv version plus a changelog note in the abstract field is standard practice; silent replacement is not.
- Anonymity timing: if the full version goes up before notification, keep it consistent with the double-blind submission rules of the current cycle (待核实 each year — the interaction between preprint posting and STOC's newly adopted anonymization is exactly the kind of policy that gets refined).
Show full SKILL.md (361 more words)Show less
Worked vignette: a construction found by search
Suppose a submission's key lemma asserts that a particular 11-vertex gadget with a rare expansion property exists, and the gadget was found by a randomized search over labeled graphs. The evidence plan under STOC norms:
- The lemma's proof in the appendix presents the gadget explicitly (adjacency list in a figure) and verifies its property analytically where feasible; if the property check is itself a finite computation, the proof says exactly what was computed and by what procedure.
- The search program is credited in one sentence and never trusted: "the gadget was located by simulated annealing; its properties are verified below."
- A 25-line standalone checker that re-verifies the property from the adjacency list ships as an arXiv ancillary file with the full version.
- Nothing about the search's hyperparameters, runtime, or seed enters the paper — those matter only when a nonexistence claim rests on the search, which would move the computation into the certified-proof-step regime.
Optional strengtheners, priced honestly
- A Lean/Coq mechanization of a central lemma is a strong credibility signal in the current theory climate (STOC 2026's TheoryFest even hosted a workshop on AI and theorem-proving), but state coverage precisely: which statements, which axioms, what remains informal. Overclaiming formality is worse than none.
- A reference implementation of a new algorithm helps readers, but do not let it drift into benchmark claims the paper does not make — that invites the question of why the paper is not at an experimental venue.
- The STOC 2026 opt-in LLM pre-submission feedback experiment (full paper due November 1, output visible only to authors) is a free adversarial reader for rigor, not an artifact process; treat its output as hints to verify, never as verification.
Quick decision rubric
- Claim depends on a computation → certified proof step: determinism, certificate, independent checker, all shipped. Non-negotiable.
- Computation only found something humans then verified → one sentence of credit; the found object carries the weight.
- Code merely illustrates → public repository after acceptance, linked from the full version; keep it out of the reviewed pages.
- Someone suggests an "artifact appendix" with environment tables → decline; that is another venue's ritual and reads as venue confusion here.
Output format
[Evidence stack] <object -> location -> binding or optional>
[Computer-assisted steps] none / certified (checker shipped?) / uncertified <- fix
[Full-version audit] complete / gaps: <list>
[Mechanization] none / partial (coverage stated?) / full
[Release plan] <arXiv/ECCC timing, anc files, repository>© 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 STOC-Skills/skills/stoc-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Stoc 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 |
|---|---|---|---|---|---|---|
| Stoc Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | 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 Stoc Artifact Evaluation
What does Stoc Artifact Evaluation do?
A skill your agent uses when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is…. Stoc Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC, plus verifiable certificates whenever a proof leans on computation, and optional mechanization.
When should I use Stoc Artifact Evaluation?
Stoc Artifact Evaluation fits situations like: deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship; given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC; plus verifiable certificates whenever a proof leans on computation; optional mechanization.
How do I install Stoc Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-artifact-evaluation -a claude-code`. Or copy the skill folder (STOC-Skills/skills/stoc-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/stoc-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Stoc Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-artifact-evaluation -a codex`. Or copy the skill folder (STOC-Skills/skills/stoc-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/stoc-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Stoc 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 stoc-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/stoc-artifact-evaluation, .gemini/skills/stoc-artifact-evaluation, .github/skills/stoc-artifact-evaluation and .opencode/skills/stoc-artifact-evaluation in your project.
What does Stoc Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Stoc Artifact Evaluation is instructions for the agent only. Our summary lists: Python 3.
Does Stoc Artifact Evaluation 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 Stoc 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 Stoc Artifact Evaluation use?
Stoc 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 Stoc Artifact Evaluation use?
About 1.7k tokens (SKILL.md is roughly 7k 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 Stoc Artifact Evaluation?
Skills that share tags, products or a category with Stoc 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 Stoc 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.