Agent skill · Audited from source
Subsection Briefs
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: Build per-subsection writing briefs (NO PROSE) so later drafting is driven by evidence and checkable comparison axes (not outline placeholders).
Cite
Cite this page
ModelsAtlas. “Subsection Briefs (WILLOSCAR/research-units-pipeline-skills)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/willoscar/subsection-briefs
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 | 1 |
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 (3)
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
LOWInsecure cryptocrypto.weak_hash · scripts/run.py:570
h = int(hashlib.md5(seed.encode("utf-8", errors="ignore")).hexdigest()[:8], 16)- Why
- No further detail recorded for this rule.
- Fix
- —
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/subsection-briefsThe 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: Build per-subsection writing briefs (NO PROSE) so later drafting is driven by evidence and checkable comparison axes (not outline placeholders).
--- name: subsection-briefs description: "Build per-subsection writing briefs (NO PROSE) so later drafting is driven by evidence and checkable comparison axes (not outline placeholders)." --- # Subsection Briefs ## Triggers & routing - **Trigger**: subsection briefs, writing cards, intent cards, H3 briefs, scope_rule, axes, clusters, 写作意图卡, 小节卡片, 段落计划. `outline/subsection_briefs.refined.ok` freezes reviewed briefs only while the marker is newer than the briefs, declared inputs, domain packs, and generator. Stale markers are removed before backed-up regeneration. Build deterministic H3 brief cards from outline + mapping + paper notes. Compatibility mode is active: this skill keeps the current `outline/subsection_briefs.jsonl` field contract and paragraph-plan shape while moving phrase/domain logic into `references/` and `assets/`. ## Quick Use - Run `scripts/run.py` as the deterministic materializer. - Keep the output NO PROSE: subsection-scoped plans, axes, clusters, and bridge handles only. - Preserve current downstream compatibility for `transition-weaver`, `writer-context-pack`, and `subsection-writer`. ## Load Order Always read: - `references/overview.md` Read by task: - If `thesis` feels repetitive or copyable, read `references/thesis_patterns.md`. - If `tension_statement` is too generic, read `references/tension_patterns.md`. - If axes are weak or domain-biased, read `references/axis_catalog_generic.md` and `references/axis_catalog_llm_agents.md`. - If transition handles feel bland, read `references/bridge_terms.md`. - For calibration, read `references/examples_good.md`. Machine-readable assets: - `assets/phrase_packs/thesis_patterns.json` - `assets/phrase_packs/bridge_contrast.json` - `assets/domain_packs/generic.json` - `assets/domain_packs/llm_agents.json` - `assets/domain_packs/embodied_ai.json` - `assets/domain_packs/rag_evaluation.json` - `assets/domain_packs/text_to_image.json` The script loads these packs first; patch them before changing Python when the issue is phrasing, domain routing, axis inventory, cluster purity, or lexical bridge coverage. ## Inputs - `outline/outline.yml` - `outline/mapping.tsv` - `papers/paper_notes.jsonl` - Optional: `GOAL.md` - Optional: `outline/claim_evidence_matrix.md` ## Output - `outline/subsection_briefs.jsonl` Required record shape remains compatibility-preserving: - identity: `sub_id`, `title`, `section_id`, `section_title` - planning core: `rq`, `thesis`, `scope_rule`, `axes`, `bridge_terms`, `contrast_hook`, `tension_statement` - evidence hooks: `evaluation_anchor_minimal`, `required_evidence_fields`, `clusters` - execution plan: `paragraph_plan`, `evidence_level_summary`, `generated_at` ## What `run.py` Should Do - Read outline, mapping, and notes. - Normalize subsection seeds from outline bullets. - Load thesis/tension/domain-axis packs from `assets/`. - Produce stable JSONL records with the existing contract. ## What `run.py` Should Not Do - Do not invent papers, citations, or claims. - Do not emit reader-facing narrative prose. - Do not hardcode domain-specific sentence templates when an asset pack can hold them. ## Block / Reroute - If outline, mapping, or notes are missing, stop. - If evidence is thin, keep `thesis`/`tension_statement` conservative and let downstream evidence skills strengthen the subsection. - If contrast clusters collapse into overlapping paper pools, reroute before writing: after removing bridge papers, each side should still retain at least 2 unique papers. - Use `bridge_terms` to surface concrete lexical handles that later evidence/ranking stages can still match (`OOD`, `sim-to-real`, `world model`, `failure detector`, specific benchmark families), not only generic axis names. - Prefer domain-pack `cluster_rules` over ad-hoc bootstrap overlaps when the mapped set is already large enough to support disjoint clusters. - Do not “fix” thin evidence by inventing more specific axes or stronger claims. ## Execution notes When running in compatibility mode, `scripts/run.py` currently reads: - `outline/outline.yml` for section/subsection structure - `outline/mapping.tsv` for paper-to-subsection coverage - `papers/paper_notes.jsonl` for structured evidence - `GOAL.md` for topic/domain cues - `outline/claim_evidence_matrix.md` as optional supporting context when present ## Script ### Quick Start - `uv run python .codex/skills/subsection-briefs/scripts/run.py --workspace <workspace>` ### All Options - `--workspace <dir>` - `--unit-id <id>` - `--inputs <a;b;...>` - `--outputs <a;b;...>` - `--checkpoint <C*>` ### Examples - `uv run python .codex/skills/subsection-briefs/scripts/run.py --workspace <workspace>` ## Troubleshooting - If the wrong domain pack is selected, inspect `GOAL.md` and the asset packs before changing the script. - If briefs sound too generic, adjust the phrase/domain packs instead of adding more Python prose. - If `papers/paper_notes.jsonl` is thin, reroute to note extraction rather than inventing axes.
Excerpt, first 5,020 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 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/subsection-briefs/)
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/subsection-briefs/)
<a href="https://modelsatlas.com/skills/willoscar/subsection-briefs/"><img src="https://modelsatlas.com/skills/willoscar/subsection-briefs/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Subsection Briefs
What does the Subsection Briefs skill do?
Is Subsection Briefs safe to install?
What can Subsection Briefs access on my machine?
Which assistants does Subsection Briefs 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 Subsection Briefs skill do?
- Is Subsection Briefs safe to install?
- What can Subsection Briefs access on my machine?