harvest-feed — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited harvest-feed (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Scan the current conversation history and generate 4-5 feed entry suggestions for the digital garden at ~/work/projects/digital-garden/.
Prioritize these (highest to lowest):
Skip anything generic that a reader could easily find in official docs.
Review the full conversation. For each candidate, note:
Read references/content-formats.md for exact schemas.
Pick the best type for each:
| Signal | Type |
|---|---|
| Quick observation, one insight, 2-5 sentences | Discovery (learning) |
| A useful link/resource worth sharing | Discovery (resource) |
| Progress on an active project | Project activity entry |
For project activity entries, check which project file to append to:
ls ~/work/projects/digital-garden/src/content/projects/For each entry, suggest one or more artefacts that would make the post more engaging. Think about what the reader would want to see alongside the text.
Types of artefacts to suggest:
| Artefact | When to suggest | Example |
|---|---|---|
| Screenshot | UI changes, tool output, terminal results, before/after comparisons | "Screenshot of the Shopify admin after product import" |
| Code snippet | A specific command, config block, or script that made things work | Use the code + codeLanguage fields |
| Before/after pair | Migrations, redesigns, refactors | "Screenshot of WooCommerce vs Shopify product page" |
| Terminal output | CLI tool results, build logs, error messages that tell the story | Screenshot or code block of the relevant output |
| Diagram or flow | Architecture decisions, data pipelines, workflow explanations | "Simple flow: WooCommerce export → script → Shopify CSV → upload" |
| Short screen recording | Multi-step workflows, interactive features | "Record the /harvest-feed flow from invocation to file creation" |
Rules:
public/captures/ (or public/images/projects/[project-slug]/ for project activity)Present all 4-5 suggestions in a numbered list. For each show:
## [N]. [Title]
**Type**: Discovery (learning) / Discovery (resource) / Project update → [project-slug]
**Why it's worth sharing**: One sentence on the novelty or usefulness.
**Suggested artefact**: What to capture and where to save it.
[Draft content — full markdown ready to paste into a file]After presenting all suggestions, ask:
Which of these should I create? (e.g. "1, 3, 5" or "all" or "skip 2") For entries with suggested screenshots — do you want to capture those now, or add them later?
For approved entries, create the actual files:
src/content/discoveries/YYYY-MM-DD-slug.mdactivity: array in the existing project fileUse today's date. Set draft: true so nothing publishes until the user explicitly flips it.
If artefacts are code snippets, include them directly using code and codeLanguage fields.
For image artefacts, add to the images array with the expected path. Leave a TODO note if the screenshot still needs to be captured.
REQUIRED: Read references/writing-style.md before drafting any content. It defines voice, titles, punctuation rules, structure, and what to avoid.
Critical rules (always apply, even without loading the guide):
title values in double quotesBefore writing, review these examples to match the tone and structure of existing posts:
| Example | Type | What it demonstrates |
|---|---|---|
| examples/learning-with-images.md | Learning | Multi-tool comparison, inline images, personal take as blockquote |
| examples/resource-concise.md | Resource | Audience-targeted intro, concise, no claims |
| examples/learning-long-form.md | Learning | Technical depth, sections, prompt inclusion |
| examples/resource-minimal.md | Resource | One-liner commentary, minimal |
| examples/resource-premise-driven.md | Resource | Premise-first framing, context before link |
Match the closest example to each entry you draft.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.