qfeed

Files gated findings as tasks into a team queue via the session-viz tasks API.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/QSchlegel/session-viz --skill qfeed-qschlegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qfeed
Source: https://github.com/QSchlegel/session-viz/tree/main/plugins/session-viz/skills/qfeed
Command: npx skills add https://github.com/QSchlegel/session-viz --skill qfeed-qschlegel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Audit findings from coding-agent transcripts are only useful if they become tracked work, but filing a task for every finding creates noise. qfeed turns only the findings that passed strict evidence gates into tasks in your team's queue, and never files anything until you explicitly approve it. ## Core Features & Use Cases - Gated task filing: Four detectors (qruns:stalled, qruns:schema, qdoctor:gap, qship:ritual) each apply their own thresholds, so only findings with real evidence become task candidates. - Review-before-push workflow: Run the script bare to see qualifying findings, use --review to read full task bodies, then --push --yes to file them; --push without --yes refuses. - Idempotent scheduling and cleanup: Tasks carry a stable source key the server upserts on, so daily runs refresh evidence instead of duplicating tasks, and --close retires only tasks this tool filed whose finding has gone away. - Use Case: After a /qruns audit reveals a scheduled job that ran 20 times delivering nothing, run qfeed to file that stalled task into the shared queue so a teammate can accept and fix it. ## Quick Start Ask the assistant to run qfeed to list which gated findings qualify as tasks, review them, and then file the approved ones into the team queue.

Frequently Asked Questions about qfeed

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

FAQPage Schema
How do I file tasks from session-viz audit findings?▼

Run qfeed.mjs with no flags to list qualifying findings, then with --review to read the task bodies, and finally with --push --yes to file them. The --push flag without --yes refuses and tells you to review first.

What findings qualify as tasks in qfeed?▼

Four detectors apply strict gates: stalled recurring tasks need at least 5 runs with zero deliveries, schema failures need 25+ structured runs at over twice the fleet median, qdoctor findings must be level 'gap', and rituals need 3+ sessions, 3+ median tools, and 20+ characters.

Why does qfeed fail with a token scope error?▼

The /v1/tasks route requires a collab-scoped token and rejects contrib tokens. Run qsetup.mjs --scope collab to mint one, noting that only a workspace admin can approve that scope.

Why does qfeed --close return a 409 error?▼

A task can only move from accepted to done, and newly filed tasks start in draft, so closing an unaccepted task returns '409 illegal transition draft → done'. Withdraw the stale task in the console instead of accepting it on someone's behalf.

Can qfeed run on a daily schedule without duplicating tasks?▼

Yes. Each task carries a stable source key like qruns:stalled:<task> and the server upserts on it, so repeat runs refresh evidence on the existing task rather than filing duplicates. Task state is never reset on update.