seed

Validate a source file, archive it, and create an extract task in the queue.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/wtyler2505/ProtoPulse --skill seed-wtyler2505
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seed
Source: https://github.com/wtyler2505/ProtoPulse/tree/main/.agents/skills/seed
Command: npx skills add https://github.com/wtyler2505/ProtoPulse --skill seed-wtyler2505

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seed files into the processing queue by validating existence, checking duplicates, archiving the source, and creating an extract task for downstream processing.

Core Features & Use Cases

  • Duplicate detection across queue and archive to prevent duplicate work.
  • Immediate archiving of sources (even living docs) to establish a stable reference.
  • Automatic creation of an extract task and queue entry to kick off processing.
  • Clear next steps and batch guidance for operators.
  • Use case: seed a new document for extraction or analysis in the pipeline.

Quick Start

Seed a file by running /seed followed by the file path.

Frequently Asked Questions about seed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I seed files into a processing queue safely?

To seed files safely, run /seed followed by the file path. The workflow validates file existence, checks duplicates across queue and archive, archives the source, and creates an extract task to kick off downstream processing deterministically.

How does duplicate detection work when seeding documents for extraction?

Duplicate detection checks the incoming source file against both the current processing queue and the archive. This prevents duplicate work by ensuring the same document is not processed twice across the pipeline.

Do I need a specific directory structure to queue files for automation?

Yes, this workflow requires a queue and archive structure to function correctly. It applies to individual files originating in the inbox, which are then moved to the archive to establish a stable reference.

What is the best way to archive source files before downstream task processing?

The best way is immediate archiving upon seeding. This workflow archives the source file, even living docs, to establish a stable reference before creating an extract task and updating the queue.

Why does my file queue workflow create duplicate extract tasks?

Duplicate extract tasks occur without proper duplicate detection. This workflow prevents duplicates by checking the queue and archive before creating an extract task, ensuring deterministic handling.