Skip to content
Back to skills

Harvest

ASecurity

Report where a session missed moo's standard — the agent asks only while stating intent and shape, then works on its own — as issues a builder can act on. Pass a session id to report on a past session instead of this one.

  • 34 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentsgo

Security analysis

A100/100

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

Scanned September 29, 2026

npx -y skills add saadshahd/moo.md --skill harvest --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Harvest?

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

Security grade badge for Harvest
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/saadshahd-harvest/badge)](https://www.skillsdirectory.com/skills/saadshahd-harvest)

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: harvest
description: Report where a session missed moo's standard — the agent asks only while stating intent and shape, then works on its own — as issues a builder can act on. Pass a session id to report on a past session instead of this one.
disable-model-invocation: true
---

harvest captures and reports. It never drafts, builds or fixes a skill: builders do that from the report.

## Read

Run `${CLAUDE_SKILL_DIR}/scripts/read.sh <id>`, where `<id>` is `$ARGUMENTS` if given, else `${CLAUDE_SESSION_ID}`. It fails → show its error and stop.

Its output is the only source. A turn you cite is a numbered turn in it. It cuts long agent text; `read.sh <id> <turn>` prints one turn whole.

## Detect

Read every file in `${CLAUDE_SKILL_DIR}/kinds/`. Each names one way a session misses the standard: its sign in the marked turns, what counts, what doesn't, the evidence it needs. Walk the turns once per kind and collect each flow that meets it with the evidence it asks for. A flow without that evidence is dropped, not guessed at — but first read whole every cut turn it cites.

## Name the opportunity

For each flow, one of:

| The flow shows | Opportunity |
|---|---|
| An installed moo skill covers the need and failed, or did not fire | Improve that skill, named |
| No installed moo skill covers it | A new skill |
| Steps the user gave more than once | A reusable piece |

State the need — what must happen, and when — never the unit that would carry it. Check the installed list `read.sh` prints before calling anything new: a need an installed skill covers is an improvement to it.

## Value

Name which of moo's four outcomes the fix serves: reduce decision regret, increase conceptual clarity, fewer but stronger artifacts, preserve the capacity to own what you produce. None → drop the flow.

## Draft

One issue per flow, laid out as `${CLAUDE_SKILL_DIR}/issue.md`, into a file from `mktemp`. Quote the user only from `read.sh` turns. Put a placeholder where a repo, file, service, person or remote would go.

## Scrub

Run `${CLAUDE_SKILL_DIR}/scripts/scrub.sh <id> <draft>` on each draft. Exit 1 → replace each term it lists with a placeholder and run it again. Never show a draft that has not passed.

## Show

Every flow, ranked by the weight of its evidence: most turns cited and clearest sign first. For each, the draft in full and its file path. Then ask the reporter which to file.

## File on yes

Only the drafts the reporter says yes to, as shown:

`tail -n +2 <draft> | gh issue create -R saadshahd/moo.md --label harvest --title "$(sed -n '1s/^Title: //p' <draft>)" --body-file -`

The draft's first line is its title, so the body starts after it.

Show each issue's URL. A draft changed after the yes goes back through Scrub and Show.

Never:

- Propose a new unit where an installed one covers the need.
- Write code or unit files.
- File without the reporter's yes to the exact text.

Files in this skill

  • HYPOTHESIS.md2.6 KB
  • SKILL.md3 KB

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.