Agent skill · Audited from source
Survey Visuals
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: Draft non-prose visuals artifacts (timeline, figure specs) for a survey, grounded in evidence and using citation keys from `citations/ref.bib`.
Cite
Cite this page
ModelsAtlas. “Survey Visuals (WILLOSCAR/research-units-pipeline-skills)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/willoscar/survey-visuals
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/survey-visualsThe 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: Draft non-prose visuals artifacts (timeline, figure specs) for a survey, grounded in evidence and using citation keys from `citations/ref.bib`.
---
name: survey-visuals
binding: library
description: "Draft non-prose visuals artifacts (timeline, figure specs) for a survey, grounded in evidence and using citation keys from `citations/ref.bib`."
---
# Survey Visuals (timeline + figure specs; NO PROSE)
## Triggers & routing
- **Trigger**: survey visuals, timeline, figures, visuals, 图表, 时间线, figure spec.
- **Use when**: survey 的 C4(NO PROSE),已有 outline + claim/evidence + citations,需要先把时间线/图规格落盘。
This skill creates non-prose artifacts that make the writing stage less template-y:
- timeline / evolution bullets
- figure specs (what to draw, why it matters, what papers support it)
## Load Order
Always read:
- `references/overview.md`
- `references/figure_archetypes.md`
Read by task:
- `references/timeline_patterns.md` when building timeline milestones
Machine-readable assets:
- `assets/figure_templates.yaml` — figure archetype specifications (extensible without code changes)
## Script Boundary
Use `scripts/run.py` only for:
- deterministic assembly of timeline bullets from paper_notes + bibkeys
- table generation from outline + mapping
- figure spec skeleton generation using `assets/figure_templates.yaml`
Do not treat `run.py` as the place for:
- hardcoded figure descriptions or narratives
- milestone selection heuristics that should be inspectable from references
Tables are handled by dedicated table skills:
- `table-schema` -> `outline/table_schema.md`
- `table-filler` -> `outline/tables_index.md` (internal index)
- `appendix-table-writer` -> `outline/tables_appendix.md` (reader-facing Appendix tables)
## Inputs
- `outline/outline.yml`
- `outline/claim_evidence_matrix.md`
- `papers/paper_notes.jsonl`
- `citations/ref.bib`
## Outputs
- `outline/timeline.md`
- `outline/figures.md`
## Workflow inputs (explicit)
- Use `outline/outline.yml` + `outline/claim_evidence_matrix.md` to decide what to visualize.
- Use `papers/paper_notes.jsonl` for year/milestone candidates.
- Use only citation keys from `citations/ref.bib`.
## Workflow (heuristic)
1) Read the outline + claim-evidence matrix and pick recurring comparison axes.
2) Timeline (`outline/timeline.md`):
- Write year -> key milestone bullets (aim for breadth and citations).
3) Figures (`outline/figures.md`):
- Write 2-4 figure specs that a human could draw:
- purpose (what insight this figure communicates)
- required elements (boxes/arrows/axes)
- what papers support each element (cite keys)
4) Use only citation keys present in `citations/ref.bib`.
## Quality checklist
- [ ] No `TODO` and no `<!-- SCAFFOLD ... -->` markers remain in the outputs.
- [ ] `outline/timeline.md` contains >=8 year bullets and each bullet has >=1 citation marker `[@...]`.
- [ ] `outline/figures.md` contains >=2 figure specs and each mentions at least one supporting citation.
## Helper script (optional)
### Quick Start
- `uv run python .codex/skills/survey-visuals/scripts/run.py --help`
- `uv run python .codex/skills/survey-visuals/scripts/run.py --workspace <workspace>`
### All Options
- `--workspace <workspace>` (required)
- `--unit-id <id>` (optional; used only for runner bookkeeping)
- `--inputs <a;b;c>` (optional; defaults to the four Inputs listed above)
- `--outputs <timeline_rel;figures_rel>` (optional; defaults to `outline/timeline.md;outline/figures.md`)
- `--checkpoint <C#>` (optional; ignored by the helper)
### Examples
- Generate timeline + figures with defaults:
`uv run python .codex/skills/survey-visuals/scripts/run.py --workspace <workspace>`
- Generate to custom output paths:
`uv run python .codex/skills/survey-visuals/scripts/run.py --workspace <workspace> --outputs outline/timeline.md;outline/figures.md`
### Notes
- The helper is intentionally minimal and never overwrites non-placeholder artifacts.
- In strict mode it blocks only if placeholder markers remain (and if minimum timeline/figure requirements are not met).
## Troubleshooting
### Issue: timeline is thin or citation-free
Fix:
- Prefer fewer, higher-signal milestones, but ensure each bullet has >=1 `[@...]`.
- Route upstream if notes are thin: strengthen `paper-notes` / `evidence-draft` rather than padding.
### Issue: figure specs read like prose
Fix:
- Keep specs as draw-instructions: purpose + elements + what each element is supported by (cite keys).
- Move narrative explanation into the main text; this file should stay non-prose.Excerpt, first 4,428 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
uv run python .codex/skills/survey-visuals/scripts/run.py --workspace <workspace> uv run python .codex/skills/survey-visuals/scripts/run.py --workspace <workspace> --outputs outline/timeline.md;outline/fig
git clone https://github.com/WILLOSCAR/research-units-pipeline-skills git -C research-units-pipeline-skills checkout 81994516a430
Commands as the repository documents them: shown, never run by us. Our verdict covers commit 81994516a430 only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Codex | Mentioned in its text, not tested | Skills for Codex · About Codex |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
81994516a430
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/willoscar/survey-visuals/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
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`).
Add this badge to your README
[](https://modelsatlas.com/skills/willoscar/survey-visuals/)
<a href="https://modelsatlas.com/skills/willoscar/survey-visuals/"><img src="https://modelsatlas.com/skills/willoscar/survey-visuals/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Survey Visuals
What does the Survey Visuals skill do?
Is Survey Visuals safe to install?
What can Survey Visuals access on my machine?
Which assistants does Survey Visuals work with?
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 Survey Visuals skill do?
- Is Survey Visuals safe to install?
- What can Survey Visuals access on my machine?