Skip to content
Back to skills

Source Pass Harvester

ASecurity

Use when mining external JS/TS libraries, runtimes, papers, benchmark suites, bug corpora, or production systems for ideas that should become local tests, fuzzers, benchmarks, or evidence notes.

  • 6 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 12, 2026
research

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add siliconjungle/-shapeshift-labs-evidence-kit --skill source-pass-harvester --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Source Pass Harvester?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Source Pass Harvester
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/siliconjungle-source-pass-harvester/badge)](https://www.skillsdirectory.com/skills/siliconjungle-source-pass-harvester)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: source-pass-harvester
description: Use when mining external JS/TS libraries, runtimes, papers, benchmark suites, bug corpora, or production systems for ideas that should become local tests, fuzzers, benchmarks, or evidence notes.
---

# Source Pass Harvester

Source passes turn external inspiration into local evidence. They are a fetch/cache/classify/transfer loop, not just agent-written notes.

## Workflow

1. Search local evidence memory first:

```sh
npm run docs:perf:search -- <topic terms>
npm run research:list
```

2. Define the question: what weakness or workload are we trying to learn about? If the target project still lacks target-owned contracts, corpus seeds, or benchmark fixtures, use `target-evidence-designer` first.

3. Add or update a repeatable fetcher and source config:

```sh
npx evidence-kit add-source-fetcher --name <topic>
npm run research:fetch -- <topic>
```

Fetchers should cache external repos under `research/repos/<topic>/`, raw data or metadata under `benchmarks/data/<topic>/`, and write `research/repos/<topic>/manifest.json`.

4. Inspect fetched material for test practice, fuzzer structure, benchmark fixture shape, failure handling, package boundaries, startup budgets, and corpus curation.

5. Transfer ideas into local artifacts:
   - tests,
   - fuzzer corpus cases,
   - benchmark fixtures,
   - package-boundary checks,
   - iteration/research notes.

6. Keep runtime dependencies out unless the benchmark proves they are worth it.
7. Record rejected ideas explicitly.

## Decision Filter

Accept an idea only when it is:

- generic enough for the project contract,
- backed by a local test or benchmark,
- not hard-coded to the source project's domain names,
- not adding hidden state or dependencies without a clear contract.

## Output

Create or update a `research/*-sources.md` note and an `iterations/*-source-pass.md` note. Include source names, URLs, commits or hashes, local cache paths, manifest path, commands, accepted transfers, rejected transfers, and artifact paths.

Files in this skill

  • SKILL.md2 KB
  • agents/openai.yaml303 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.