skills.rest
Noetfield-Systems
Noetfield-SystemsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sina-sourcea-worker

Executes single-task worker turns with inbox draining, validation, and broker-submitted receipts.

Updated Jun 20, 2026
Search Tags:#validation#task execution#registry#receipt verification#worker automation#inbox drain#broker submit
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill sina-sourcea-worker-noetfield-systems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sina-sourcea-worker
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/sina-sourcea-worker
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill sina-sourcea-worker-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It enforces a disciplined, auditable worker loop for the SourceA Goal 1 pipeline, preventing stale chat-based execution, batch overreach, and unverified progress claims by requiring disk-based receipts for every turn. ## Core Features & Use Cases - INBOX Drain Execution: Reads pending tasks from the on-disk worker inbox and executes exactly one sa task per turn under CHECK, ACT, or VERIFY roles. - Honest Receipt Verification: Validates work through read-only validators, registry hygiene checks, and receipt files on disk rather than chat claims. - Broker Submission: Ends every turn with a parseable WORKER_ROUND_REPORT YAML block submitted via the goal1 lane broker. - Use Case: When a headless auto-run delivers an sa-#### task, run the session gate, execute the single assigned role, verify with fast validators, and submit the round report to the broker. ## Quick Start Ask the agent to run the worker inbox for the current pending sa task and submit the round report to the broker.

Frequently Asked Questions about sina-sourcea-worker

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

FAQPage Schema
How do I run a worker turn for an sa task?▼

Run the session gate script with the worker role, check the on-disk inbox for a pending prompt, then execute exactly one sa task under the assigned CHECK, ACT, or VERIFY role. End the turn by submitting a WORKER_ROUND_REPORT block to the goal1 lane broker.

What is the difference between CHECK, ACT, and VERIFY roles?▼

CHECK reads the task file and runs read-only validators to report gaps without implementing. ACT applies a minimal diff for the bound sa_id only. VERIFY runs validators, produces a receipt, and performs honest closeout without adding new scope.

Why must receipts exist on disk instead of chat claims?▼

Disk receipts are the only valid proof of progress because chat claims and registry stamps can be fabricated or stale. The broker CHECK-ACT-VERIFY chain and receipt files provide auditable evidence that work actually completed.

Can I process multiple sa tasks in one turn?▼

No, the skill enforces one sa per turn as a hard law. Batch processing, multi-sa closeouts, and unattended runs are explicitly forbidden and counted as instant failures.

What happens when the feasibility gate blocks a task?▼

When the feasibility gate returns STOP_INJECT or FEASIBILITY_BLOCKED, the worker reports BLOCKED and does not implement anything. This prevents executing tasks that fail pre-flight validation.

Related Skills

Explore More Software Engineering Skills→
adelabdelgawadadelabdelgawad

celery-worker

Configure Celery workers with late acknowledgments, time limits, and queue routing.

Community
Advanced
kortix-aikortix-ai
20.1k

autowork-team

Coordinate parallel autowork tasks across multiple lanes with bounded concurrency.

Official
Advanced
LudwigAJLudwigAJ

gatekeeper-worker

Validate mission gate claims against evidence and workflow rules.

Community
Advanced
alexizationalexization

boundary-check

Validate active phase write paths and trigger replanning for out-of-scope changes.

Community
Intermediate