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

Agent skill · Audited from source

Extraction Form

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

★ 513pushed 14 days ago
✓SAFEGrade B · 89/100 · 19 Oct 2026 · 8199451
513repo 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: Use when `evidence-review` has screened includes and needs a schema-aligned extraction table.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Extraction Form (WILLOSCAR/research-units-pipeline-skills)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/willoscar/extraction-form

Trust audit

Audit 0.4.1 · source read 19 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 · 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/extraction-formThe 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 `evidence-review` has screened includes and needs a schema-aligned extraction table.

---
name: extraction-form
description: "Use when `evidence-review` has screened includes and needs a schema-aligned extraction table."
---

# Extraction Form

## Triggers & routing

- **Trigger**: extraction form, extraction table, data extraction, 信息提取, 提取表.
- **Use when**: `evidence-review` 在 screening 后进入 extraction(C4),需要把纳入论文按字段落到 CSV 以支持后续 synthesis。


Transforms screened include rows plus protocol schema into the analysis table used by `evidence-review`.

## Inputs

Required:
- `papers/screening_log.csv`
- `output/PROTOCOL.md`

Optional:
- `papers/paper_notes.jsonl`

## Output

- `papers/extraction_table.csv`

## Contract

The table must:
- contain one row per included paper
- preserve provenance columns (`paper_id`, `title`, `year`, `url`)
- include protocol-defined extraction fields
- keep narrative residue in `notes`, not in schema columns

## Script boundary

`scripts/run.py` should:
- parse the extraction schema from the protocol
- filter `include` rows
- materialize a normalized CSV

## Acceptance

- output exists
- include rows map 1:1 to extraction rows
- schema matches `output/PROTOCOL.md`

## Non-goals

- synthesis writing
- bias scoring

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

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

  1. ✓SAFE B 89 / 100

    first audit · source 81994516a430

Questions about Extraction Form

What does the Extraction Form 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 Extraction Form 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 Extraction Form access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (81994516a430), read on 2026-10-19. 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.