Agent skill

Focs Supplementary

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

MITAuto-check passed

Install Focs Supplementary

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-supplementary --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-supplementary .claude/skills/focs-supplementary && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "focs-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-supplementary into .claude/skills/focs-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-supplementary", 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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-supplementary

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-supplementary --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .agents/skills/focs-supplementary && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "focs-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-supplementary into .agents/skills/focs-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-supplementary", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-supplementary --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .cursor/skills/focs-supplementary && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "focs-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-supplementary into .cursor/skills/focs-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-supplementary", 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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path FOCS-Skills/skills/focs-supplementary

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-supplementary --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .gemini/skills/focs-supplementary && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "focs-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-supplementary into .gemini/skills/focs-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-supplementary", 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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-supplementary

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-supplementary .github/skills/focs-supplementary && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "focs-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-supplementary into .github/skills/focs-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-supplementary", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-supplementary --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .opencode/skills/focs-supplementary && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "focs-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-supplementary into .opencode/skills/focs-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-supplementary", 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-supplementary
GitHub stars: 1.2k
Token cost: ~1.6k tokens
SKILL.md length: 775 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 4 steps: Claim audit: nothing asserted after page… → Navigation audit: window → proof in one… → Self-containment audit: each proof… → …
Proof placement
SKILL.md covers The two-reader contract, Organizing the discretionary…, Pointer discipline and The window boundary is a…, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Focs Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when architecting everything after page ten of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — a venue with no separate supplement channel where the paper itself continues past the guaranteed-read window — covering body organization, proof placement, and navigation for the discretionary reader.

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.

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

Proof placement
Navigation for the discretionary reader

Example prompts

“/focs-supplementary”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Claim audit: nothing asserted after page 10 that is not stated within it.
Navigation audit: window → proof in one hop for every statement.
Self-containment audit: each proof section readable given only the
Anonymity audit: pages 11+ leak identity as often as page 1 — grant

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 latex).
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

Focs Supplementary loads about 1.6k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 775 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~86
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

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). 775 words, ~1,551 tokens.

Download SKILL.mdSave it as .claude/skills/focs-supplementary/SKILL.md (or your agent's skills folder).

name: focs-supplementary
description: Use when architecting everything after page ten of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — a venue with no separate supplement channel where the paper itself continues past the guaranteed-read window — covering body organization, proof placement, and navigation for the discretionary reader.

FOCS Supplementary

FOCS has no supplementary-material upload, no appendix size cap, and no separate supplement deadline: the submission is one PDF, the CFP encourages it to be the full version, and everything beyond the abstract, references, and first ten pages is read at the committee's discretion (2026 CFP, checked 2026-07-08). "Supplementary material" at this venue therefore means the rest of your own paper — pages eleven onward — and the design question is how to serve two readers at once: the committee member who stops at page ten, and the assigned expert who reads to the end.

The two-reader contract

Reader	What they read	What pages 11+ must give them
Breadth reviewer (any PC member)	Window only	Nothing — the window must be self-sufficient; pages 11+ may not carry any claim absent from it
Depth reviewer / subreferee	Window, then targeted dives	Fast navigation from each windowed statement to its complete proof, with no re-derivation required
Post-acceptance community	The public full version	The same body, now the record of correctness for a decade

The contract's first clause is the one authors break: introducing a new result, a stronger bound, or a hidden assumption after page ten. Discretionary pages can prove anything, but may announce nothing.

Organizing the discretionary body

A structure that has served full-version submissions well:

latex

% pages 1-10: intro, overview, formal statements (focs-writing-style)
\section{Preliminaries}                 % p.11+: full notation, standard facts
\section{Proof of Theorem 1}            % one top-level section per result
  \subsection{The key lemma}            % mirrors the overview's decomposition
  \subsection{From Lemma 3.1 to Theorem 1}
\section{Proof of Theorem 2}
\appendix
\section{Deferred calculations}         % mechanical verifications only
\section{Certificate for Lemma 4.7}     % computed-step documentation
                                        % (focs-experiments)

Design rules embedded there:

Mirror the overview. The depth reviewer arrives holding the proof sketch from pages 3–6; the body's section tree should be that sketch made formal, in the same order with the same lemma names. A body organized differently from its own overview doubles refereeing work.
One theorem, one section. Interleaved proofs (Lemma 6 needed by both Theorem 1 and 2) go in the earliest section that needs them, with a forward pointer from the later one.
Appendices are for the mechanical. Reserve \appendix for calculations a reader could reproduce but should not have to: routine concentration arguments, case tables, computed certificates. A conceptually essential proof placed in an appendix reads as an attempt to hide its weakness.

Pointer discipline

Every formal statement inside the window carries an explicit address for its proof ("proved in Section 5.2"), and every body section opens by naming which windowed statement it discharges. Concretely test the navigation: a reader who doubts only Theorem 2 should reach its complete proof in one jump and find it self-contained given the preliminaries — not dependent on notation invented mid-proof of Theorem 1.

The window boundary is a design object

Page ten's edge deserves deliberate placement. Ending the window mid-proof wastes it; ending with the organization note leaves the breadth reader with a map in hand. If the formal statements run long (many theorems, heavy definitions), compress preliminaries rather than pushing statements past the edge — a definition can be informal-plus-pointer inside the window ("(formal version: Definition 11.2)") but a theorem cannot. Check the boundary on the compiled PDF, not the source: LaTeX pagination shifts, and a statement that drifted to page eleven during deadline-week edits is invisible in the diff.

Show full SKILL.md (279 more words)Show less

Length judgment

No cap does not mean no cost. Referees allocate finite hours per paper; a 70-page submission whose last 30 pages are routine variations taxes exactly the reader you most need. Calibration:

Include every proof needed for correctness — completeness is the point of full-version culture and reviewers penalize "details omitted" at this venue.
Cut or fold repetitive case analyses into representative cases plus a stated symmetry argument, with the full enumeration in an appendix or a cited certificate.
Extensions that need no new ideas ("the weighted case follows similarly") earn a remark, not a section — expand them later in the journal version.

Mechanics that keep a long document navigable

Load cleveref (or equivalent) so every reference states its own type — "Lemma 5.3" not a bare "5.3" — because the discretionary reader jumps in cold at arbitrary depth.
Hyperlink everything (hyperref with visible-but-quiet link colors); a reviewer reading on screen navigates a 50-page PDF through your links or not at all.
Repeat, do not paraphrase: when a body section restates its windowed theorem, generate the restatement with thm-restate (focs-writing-style) so the two are mechanically identical.
Number everything that might be referenced, including remarks and displayed equations used later; "the displayed inequality above" fails a reader who arrived by hyperlink.

Final check before upload

Claim audit: nothing asserted after page 10 that is not stated within it.
Navigation audit: window → proof in one hop for every statement.
Self-containment audit: each proof section readable given only the preliminaries and its own lemmas.
Anonymity audit: pages 11+ leak identity as often as page 1 — grant numbers in appendix headers and dataset paths in certificate listings are recurring offenders (focs-submission).

Files

Just SKILL.md in FOCS-Skills/skills/focs-supplementary of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Focs Supplementary 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.

Focs Supplementary compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Focs Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.6k	Automated safety check: Pass	MIT	14 days ago
Agent Repo Architectruvnet/ruflo	74k	2 repos	~3k	Automated safety check: Pass	MIT	yesterday
Hindsight Architectvectorize-io/hindsight	48k	—	~10k	Automated safety check: Notes	MIT	today
Agent V3 Integration Architectruvnet/ruflo	74k	2 repos	~2.7k	Automated safety check: Pass	MIT	yesterday
Agent V3 Security Architectruvnet/ruflo	74k	2 repos	~1.5k	Automated safety check: Pass	MIT	yesterday
Backend Architectdavila7/claude-code-templates	33k	8 repos	~4.6k	Automated safety check: Pass	MIT	today

Similar skills

Agent Repo Architect
ruvnet/ruflo
Agent skill for repo-architect - invoke with $agent-repo-architect
74k GitHub starsUsed in 2 repos~3k tokens
Auto-check passed
Hindsight Architect
vectorize-io/hindsight
Expert memory architect. An agent skill from vectorize-io/hindsight.
48k GitHub stars~10k tokensUpdated today
Agent WorkflowsAuto-check: notes
Agent V3 Integration Architect
ruvnet/ruflo
Agent skill for v3-integration-architect - invoke with $agent-v3-integration-architect
74k GitHub starsUsed in 2 repos~2.7k tokens
Agent WorkflowsAuto-check passed
Agent V3 Security Architect
ruvnet/ruflo
Agent skill for v3-security-architect - invoke with $agent-v3-security-architect
74k GitHub starsUsed in 2 repos~1.5k tokens
SecurityAuto-check passed
Backend Architect
davila7/claude-code-templates
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems.
33k GitHub starsUsed in 8 repos~4.6k tokens
Backend & APIsAuto-check passed
Database Architect
davila7/claude-code-templates
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.
33k GitHub starsUsed in 8 repos~4.3k tokens
DatabasesAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Focs Supplementary

What does Focs Supplementary do?

A skill your agent uses when architecting everything after page ten of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — a venue with no separate supplement channel where the…. Focs Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when architecting everything after page ten of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — a venue with no separate supplement channel where the paper itself continues past the guaranteed-read window — covering body organization, proof placement, and navigation for the discretionary reader.

When should I use Focs Supplementary?

Focs Supplementary fits situations like: proof placement; navigation for the discretionary reader.

How do I install Focs Supplementary in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a claude-code`. Or copy the skill folder (FOCS-Skills/skills/focs-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/focs-supplementary in your project. Claude Code loads it when a task matches its description.

How do I install Focs Supplementary in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-supplementary -a codex`. Or copy the skill folder (FOCS-Skills/skills/focs-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/focs-supplementary in your project. Codex loads it when a task matches its description.

Can I use Focs Supplementary 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-supplementary -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-supplementary, .gemini/skills/focs-supplementary, .github/skills/focs-supplementary and .opencode/skills/focs-supplementary in your project.

What does Focs Supplementary need to run?

SKILL.md names no scripts, command-line tools or credentials: Focs Supplementary is instructions for the agent only.

Does Focs Supplementary 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 Focs Supplementary 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 Supplementary use?

Focs Supplementary 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 Supplementary use?

About 1.6k tokens (SKILL.md is roughly 6.2k 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 Supplementary?

Skills that share tags, products or a category with Focs Supplementary: Agent Repo Architect (ruvnet/ruflo, 74k stars), Hindsight Architect (vectorize-io/hindsight, 48k stars), Agent V3 Integration Architect (ruvnet/ruflo, 74k stars) and Agent V3 Security Architect (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Focs Supplementary?

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.

Install Focs Supplementary

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

FOCS Supplementary

The two-reader contract

Organizing the discretionary body

Pointer discipline

The window boundary is a design object

Length judgment

Mechanics that keep a long document navigable

Final check before upload

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Focs Supplementary