Benchmark
affaan-m/ECC
Measure performance baselines and detect regressions across browser Core Web Vitals (LCP, INP, CLS, page weight), API endpoint latency percentiles, and build/test feedback times, with before/after…
Agent skill
Dac Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC…
MITAuto-check passed
Install Dac Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-artifact-evaluation .claude/skills/dac-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 "dac-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-artifact-evaluation into .claude/skills/dac-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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/DAC-Skills/skills/dac-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 dac-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-artifact-evaluation .agents/skills/dac-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 "dac-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-artifact-evaluation into .agents/skills/dac-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 dac-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-artifact-evaluation .cursor/skills/dac-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 "dac-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-artifact-evaluation into .cursor/skills/dac-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 DAC-Skills/skills/dac-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 dac-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills dac-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/DAC-Skills/skills/dac-artifact-evaluation .gemini/skills/dac-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 "dac-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-artifact-evaluation into .gemini/skills/dac-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 dac-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 dac-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/DAC-Skills/skills/dac-artifact-evaluation .github/skills/dac-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 "dac-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-artifact-evaluation into .github/skills/dac-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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 dac-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 dac-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/DAC-Skills/skills/dac-artifact-evaluation .opencode/skills/dac-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 "dac-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/DAC-Skills/skills/dac-artifact-evaluation into .opencode/skills/dac-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dac-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
dac-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 511 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC…
- Packaging the code
- SKILL.md covers What an EDA artifact is for at…, Packaging plan for an EDA…, The clean-machine,… and Anonymized review artifact vs…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible
What it does
Dac Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC has historically run no formal artifact-evaluation or badge-issuing track (verify per cycle), so the goal is reviewer credibility and community reuse via open EDA flows and DOI-archived releases, not an ACM badge.
Its SKILL.md is about 1.4k 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
- Packaging the code
- Flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible
- Reusable artifact — given that DAC has historically run no formal artifact-evaluation
- Badge-issuing track (verify per cycle)
Example prompts
- “/dac-artifact-evaluation”
Requirements
- Docker
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
Dac Artifact Evaluation loads about 1.4k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 511 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). 511 words, ~1,353 tokens.
Download SKILL.mdSave it as
.claude/skills/dac-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- dac-artifact-evaluation
- description
- Use when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC has historically run no formal artifact-evaluation or badge-issuing track (verify per cycle), so the goal is reviewer credibility and community reuse via open EDA flows and DOI-archived releases, not an ACM badge.
DAC Artifact Evaluation
Read the venue reality first. Unlike the software-engineering venues (FSE/ICSE/ISSTA) and the
computer-architecture venues (MICRO/ISCA/HPCA), DAC has historically not operated a standing,
badge-issuing artifact-evaluation track for research manuscripts; whether the current cycle adds
one is 待核实 (resources/official-source-map.md). So do not build for an ACM badge that DAC
does not award. Build instead for the two things that actually matter at DAC: making a skeptical
reviewer trust your QoR numbers and making the community able to reuse and cite your work.
What an EDA artifact is for at DAC
| Goal | What it buys you | How it is earned |
|---|---|---|
| Reviewer credibility | A QoR claim that reads as real, not cherry-picked | Standard benchmarks, disclosed flow, a runnable path |
| Community reuse | Citations and follow-on work built on your tool | Clean open-source release, good docs, a license |
| Contest/leaderboard standing | Recognition on ISPD/TAU/CAD-contest tasks | A tool that runs on the contest harness |
There is no badge to chase, so the design target is a package a stranger can run and a reviewer would believe — not a checklist an evaluator scores.
Packaging plan for an EDA artifact
[Flow] pin the toolchain: OpenROAD / ABC / Yosys / KLayout versions, or a Docker image;
avoid "install these commercial tools yourself" as the only path
[Benchmarks] ship or clearly reference the exact benchmark release (ISPD/EPFL/ISCAS/ITC/TAU/
CircuitNet) with its version
[PDK/library] include the open PDK/library used (Nangate/ASAP7) or document the NDA-gated one
[README] what it is; how to install; how to run one small demo in minutes; how to reproduce
each headline QoR number; expected runtime and outputs
[Mapping] an explicit table: paper claim -> script + benchmark -> expected QoR result
[Seeds] fixed seeds and a note on nondeterminism for stochastic/RL flows
[License] an OSI-approved license so others can build on it
[Archive] deposit a versioned release in a DOI-issuing archive (Zenodo/Software Heritage) after
acceptance for a stable citationThe clean-machine, bounded-time test
Even without formal evaluators, assume a reviewer or a future user gives your package a short, bounded try on a clean machine. Design the first ten minutes to succeed:
- A one-command small demo that runs a tiny circuit through your tool and prints a recognizable QoR number.
- No dependency on the authors' cluster, private PDK, or a live license server for the demo path.
- A clear separation between the fast demo and the slow full-benchmark reproduction (which may take hours on large designs — say so).
Show full SKILL.md (239 more words)Show less
Anonymized review artifact vs public release
- At submission (double-blind): if you link the artifact for reviewers, anonymize it exactly like the paper — no author/lab names, no personal repos, no cluster paths, no commercial-flow fingerprints. Reviewers are not required to open it, so it can only strengthen a paper that already stands on six pages.
- After acceptance: replace anonymized placeholders with the public, licensed, DOI-archived release cited in the camera-ready; this is the version the community reuses.
Worked vignette: packaging a placement tool + benchmarks
A paper contributes an ML-guided placer evaluated on ISPD circuits. A credible, reusable package:
a Docker image with the placer and an OpenROAD flow pre-built; a run_demo.sh that places one small
ISPD circuit and reports wirelength/DRC in under a minute; a reproduce/ directory whose scripts
regenerate each per-benchmark table with fixed seeds; a claim-to-script-to-benchmark mapping in the
README; the exact ISPD release and an open PDK; the trained model checkpoint and the train/test
design split; and an MIT/Apache license. State plainly which numbers are turnkey and which need the
slow full-suite run on a large machine.
Calibration
- Do not assume a DAC artifact badge exists; verify the current cycle before promising one.
- If DAC or a co-located workshop does introduce an artifact/open-source track in a given year, re-read its specific rules — do not assume ACM SIGSOFT-style badge names transfer.
- The payoff is credibility and citations; budget the artifact accordingly, not as a graded deliverable.
Output format
[Artifact goal] reviewer credibility / community reuse / contest harness
[Contents] tool + flow versions / benchmarks + version / PDK / model + split / license
[Ten-minute test] does install + small demo succeed on a clean machine? yes/no
[Claim mapping] claim -> script -> benchmark -> expected QoR present? yes/no
[Anon vs public] anonymized review artifact / DOI-archived public release planned? yes/no
[Badge check] does this cycle actually run an artifact track? verify -> yes/no/待核实© 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 DAC-Skills/skills/dac-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Dac 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 |
|---|---|---|---|---|---|---|
| Dac Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Benchmarkaffaan-m/ECC | 276k | 3 repos | ~654 | Automated safety check: Pass | MIT | |
| Benchmarkaffaan-m/ECC | 276k | — | ~412 | Automated safety check: Pass | MIT | |
| Benchmarkaffaan-m/ECC | 276k | — | ~330 | Automated safety check: Pass | MIT | |
| Artifacts Buildernexu-io/open-design | 100k | — | ~347 | Automated safety check: Pass | Apache-2.0 | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Benchmark
affaan-m/ECC
このスキルを使用して、パフォーマンスベースラインを測定し、PR前後の回帰を検出し、スタック代替案を比較します. An agent skill from affaan-m/ECC.
Benchmark
affaan-m/ECC
使用此技能测量性能基线，检测PR前后的回归，并比较堆栈替代方案。
Artifacts Builder
nexu-io/open-design
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
- Official
Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Web Artifacts Builder
nexu-io/open-design
Build complex claude.ai HTML artifacts with React and Tailwind.
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…
Questions about Dac Artifact Evaluation
What does Dac Artifact Evaluation do?
A skill your agent uses when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC…. Dac Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging the code, benchmarks, and flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible, reusable artifact — given that DAC has historically run no formal artifact-evaluation or badge-issuing track (verify per cycle), so the goal is reviewer credibility and community reuse via open EDA flows and DOI-archived releases, not an ACM badge.
When should I use Dac Artifact Evaluation?
Dac Artifact Evaluation fits situations like: packaging the code; flows behind an ACM/IEEE Design Automation Conference (DAC) Research Manuscript into a credible; reusable artifact — given that DAC has historically run no formal artifact-evaluation; badge-issuing track (verify per cycle).
How do I install Dac Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-artifact-evaluation -a claude-code`. Or copy the skill folder (DAC-Skills/skills/dac-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/dac-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Dac Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-artifact-evaluation -a codex`. Or copy the skill folder (DAC-Skills/skills/dac-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/dac-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Dac 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 dac-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/dac-artifact-evaluation, .gemini/skills/dac-artifact-evaluation, .github/skills/dac-artifact-evaluation and .opencode/skills/dac-artifact-evaluation in your project.
What does Dac Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Dac Artifact Evaluation is instructions for the agent only. Our summary lists: Docker.
Does Dac 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 Dac 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 Dac Artifact Evaluation use?
Dac 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 Dac Artifact Evaluation use?
About 1.4k tokens (SKILL.md is roughly 5.4k 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 Dac Artifact Evaluation?
Skills that share tags, products or a category with Dac Artifact Evaluation: Benchmark (affaan-m/ECC, 276k stars), Benchmark (affaan-m/ECC, 276k stars), Benchmark (affaan-m/ECC, 276k stars) and Artifacts Builder (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dac 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.