Agent skill · Audited from source
Snapshot Writer
skill · WILLOSCAR/research-units-pipeline-skillsLicence not declaredAudited 19 Oct 2026 · source 81994516a430
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 81994516a430 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Use when a `research-brief` workspace has a small paper set plus outline and needs a compact reader-facing briefing instead of a full survey.
Cite
Cite this page
ModelsAtlas. “Snapshot Writer (WILLOSCAR/research-units-pipeline-skills)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/willoscar/snapshot-writer
Trust audit
Audit 0.4.1 · source read 19 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 2 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | PASS | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass, no license.
Findings (2)
MEDIUMInventory / provenanceinv.symlink · .claude/skills
.claude/skills
- Why
- link not followed
- Fix
- —
LOWInventory / provenanceinv.no_license
- Why
- no LICENSE file and no repo licence
- Fix
- add a licence
Audit 0.4.1 · source sha 81994516a430 · 19 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- PublisherWILLOSCAR GitHub userOwner of the repository this skill is read from
- Source folderWILLOSCAR/research-units-pipeline-skills/.codex/skills/snapshot-writerThe exact folder we audited
- LicenceNot declaredAs the repository states it
- Commit pinned for this verdict81994516a430A new audit runs when the source changes
- Repository statusNot archivedLast push 14 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Use when a `research-brief` workspace has a small paper set plus outline and needs a compact reader-facing briefing instead of a full survey.
--- name: snapshot-writer description: "Use when a `research-brief` workspace has a small paper set plus outline and needs a compact reader-facing briefing instead of a full survey." --- # Snapshot Writer ## Triggers & routing - **Trigger**: snapshot, literature snapshot, 速览, 48h snapshot, one-page snapshot, SNAPSHOT.md. - **Use when**: 你要在 `research-brief` 流程里 24-48h 内交付一个“可读的研究速览”(bullet-first,含关键引用),而不是完整 survey。 Transforms a small core set plus a bullets-only outline into the final `research-brief` deliverable. ## Inputs Required: - `outline/outline.yml` - `papers/core_set.csv` Optional: - `GOAL.md` - `DECISIONS.md` - `queries.md` - `papers/papers_dedup.jsonl` ## Output - `output/SNAPSHOT.md` ## Script boundary `scripts/run.py` should stay a thin adapter over shared review tooling: - read outline/core-set inputs - use the concrete Goal and available abstracts instead of copying survey scaffold bullets - select bounded method/result sentences from abstracts; never duplicate full abstracts into multiple sections - build a compact pointer-heavy briefing - write `output/SNAPSHOT.md` Do not move topic-specific ranking rules or deep parsing logic into this script. ## Contract The output should: - read like a briefing, not a survey draft - stay bullets-first and compact - define the topic boundary - surface key themes - include explicit paper pointers in a stable format ## Acceptance - `output/SNAPSHOT.md` exists - includes `## Scope`, `## Key themes`, `## What to read first`, and `## Open problems / risks` - includes at least three explicit paper pointers that resolve to `papers/core_set.csv` - grounds Scope in at least one core-set paper, grounds every Key-theme bullet, and covers at least two unique core-set papers across those sections - stays within the Workflow evaluator's 100-1200 word compactness band - contains no survey-only scaffolding such as citation quotas, chapter plans, or "why this survey" narration ## Non-goals - full evidence synthesis - protocol / screening / extraction - monolithic long-form survey writing
Excerpt, first 2,080 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 8199451
git clone https://github.com/WILLOSCAR/research-units-pipeline-skills git -C research-units-pipeline-skills checkout 81994516a430
The author documents no install command, so this uses the repository directly. Our verdict covers commit 81994516a430 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
81994516a430
Similar skills
All automation skills →WILLOSCAR/research-units-pipeline-skills
Compile the Beamer tutorial deck and write a build report.
WILLOSCAR/research-units-pipeline-skills
Generate a Beamer slide deck from the final tutorial and approved module structure.
WILLOSCAR/research-units-pipeline-skills
Build a retrieval-informed chapter skeleton (`outline/chapter_skeleton.yml`) from taxonomy/core scope before stable H3 decomposition.
WILLOSCAR/research-units-pipeline-skills
Score an existing reader-facing deliverable and emit a deterministic PASS/FAIL scorecard plus bounded repair plan; use after synthesis, not to rewrite content.
WILLOSCAR/research-units-pipeline-skills
Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an `Approve C*` decision, and never treat silence or artifact existence as approval.
WILLOSCAR/research-units-pipeline-skills
Lock an ideation run into a single-source-of-truth brainstorm brief (`output/trace/IDEA_BRIEF.md`) and a replayable multi-query plan (`queries.md`).
Questions about Snapshot Writer
What does the Snapshot Writer skill do?
Is Snapshot Writer safe to install?
What can Snapshot Writer access on my machine?
How current is this page?
Sources
- github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.c — the audited source at commit 81994516a430 and every finding aboveObserved · 19 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Snapshot Writer skill do?
- Is Snapshot Writer safe to install?
- What can Snapshot Writer access on my machine?