Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Section Briefs

skill · WILLOSCAR/research-units-pipeline-skillsLicence not declaredAudited 14 Oct 2026 · source 81994516a430

★ 514pushed 9 days ago
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 8199451
514repo stars · whole WILLOSCAR/research-units-pipeline-skills

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 chapter-level briefs (`outline/section_briefs.jsonl`) from chapter skeleton plus section bindings before stable H3 decomposition.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Section Briefs (WILLOSCAR/research-units-pipeline-skills)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/willoscar/section-briefs

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high1 medium1 low0 info

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

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN2
L1 Static sourceSecrets, path traversal, supply chain, hidden codePASS0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass, no license.

Findings (2)

LOWInventory / provenanceinv.no_license
F-13 Inventory / provenanceCWE-1104Layer L0
Why
no LICENSE file and no repo licence
Fix
add a licence

Audit 0.4.1 · source sha 81994516a430 · 14 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/section-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 9 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 chapter-level briefs (`outline/section_briefs.jsonl`) from chapter skeleton plus section bindings before stable H3 decomposition.

---
name: section-briefs
description: "Build chapter-level briefs (`outline/section_briefs.jsonl`) from chapter skeleton plus section bindings before stable H3 decomposition."
---

# Section Briefs

## Triggers & routing

- **Trigger**: section briefs, chapter planning cards, section-first briefs, 章节 brief, 章级 brief.
- **Use when**: section bindings exist and the run needs chapter-level rationale and decomposition guidance before emitting stable H3 ids.


## Load Order

Always read:
- `references/overview.md`

Use `scripts/run.py` only for deterministic brief assembly:
- read `outline/chapter_skeleton.yml` for chapter IDs and target shape
- read `outline/section_bindings.jsonl` for saturation and gap signals
- read `GOAL.md` when present for run-level scope
- write `outline/section_briefs.jsonl` as planning substrate, not prose

## Inputs

- `outline/chapter_skeleton.yml`
- `outline/section_bindings.jsonl`
- Optional: `GOAL.md`

## Outputs

- `outline/section_briefs.jsonl`

## Asset contract

- `assets/output_contract.json`

## Script

### Quick Start

- `uv run python .codex/skills/section-briefs/scripts/run.py --workspace <workspace>`

### All Options

- `--workspace <dir>`: workspace containing chapter skeleton and section bindings
- `--unit-id <id>`: optional harness metadata
- `--inputs <semicolon-separated>`: optional override from `UNITS.csv`
- `--outputs <semicolon-separated>`: optional output override; default is `outline/section_briefs.jsonl`
- `--checkpoint <C*>`: optional harness metadata

### Examples

- Build chapter-level briefs from the section-first layer:
  - `uv run python .codex/skills/section-briefs/scripts/run.py --workspace <workspace> --inputs 'outline/chapter_skeleton.yml;outline/section_bindings.jsonl;GOAL.md' --outputs 'outline/section_briefs.jsonl'`

Excerpt, first 1,807 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

Download folder ↗
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

AgentStatusMore
CodexMentioned in its text, not testedSkills for Codex · About Codex
“Mentioned” means the skill’s text names the agent. We have not run it there.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 81994516a430

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/willoscar/section-briefs/badge.svg)](https://modelsatlas.com/skills/willoscar/section-briefs/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/willoscar/section-briefs/badge.svg)](https://modelsatlas.com/skills/willoscar/section-briefs/)

Questions about Section Briefs

What does the Section Briefs skill do?
Research pipelines as semantic execution units: each skill declares inputs/outputs, acceptance criteria, and guardrails. Evidence-first methodology prevents hollow writing through structured intermediate artifacts.
Is Section Briefs safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Section Briefs access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Section Briefs work with?
Its documentation mentions codex. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (81994516a430), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

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.