Skip to content

Bundled projio-feedback skill: agent-filed GitHub issues from any project

Problem

Users of projio outside the Sirota lab have no structured feedback channel. The retro skill in pixecog works well for internal projects (files issues via worklog_note to projio), but external users don't have worklog access. Workflow frictions, tool failures, and convention gaps go unreported.

Proposed solution

A bundled skill (data/skills/projio-feedback/SKILL.md) that lets the agent file GitHub issues against the projio repo on behalf of the user.

Workflow

  1. Agent reviews session — what tool calls failed, what workarounds were needed, what was unclear
  2. Agent drafts a structured issue (title, body with reproduction steps, expected vs actual behavior, project context)
  3. Agent shows the user the full issue text and asks for approval before filing
  4. Files via gh issue create --repo <projio-github-repo> --title "..." --body "..." --label user-feedback,from-agent

Issue body template

## Friction

<what happened, which tool call, what went wrong>

## Expected behavior

<what should have happened>

## Workaround

<what the user/agent did instead>

## Context

- projio version: <version>
- project kind: <generic/tool/study>
- profile: <if any>
- active subsystems: <biblio, pipeio, etc.>

Prerequisites

  • gh CLI installed and authenticated (gh auth status)
  • Skill checks auth first, gives setup instructions if missing
  • User must approve the issue text before it's posted (privacy — agent-observed friction may reference internal project details, file paths, data names)

Labels

  • user-feedback — distinguishes from manually filed issues
  • from-agent — indicates agent-generated content
  • Optional: workflow-friction, tool-bug, convention-gap based on category

Where it lives

Ships as a bundled skill in src/projio/data/skills/projio-feedback/SKILL.md. Available to any projio installation via skill_read("projio-feedback"). Can also be triggered as a /projio-feedback slash command.

Relation to retro

  • Internal projects (with worklog): continue using retro skill → worklog_note → dispatch
  • External projects (no worklog): use projio-feedback → gh issue create → GitHub
  • The two could share the friction-detection logic, but the filing mechanism differs