docs(skills): instruct agents to run hyperframes feedback after render#1785
Open
miguel-heygen wants to merge 2 commits into
Open
docs(skills): instruct agents to run hyperframes feedback after render#1785miguel-heygen wants to merge 2 commits into
hyperframes feedback after render#1785miguel-heygen wants to merge 2 commits into
Conversation
The `hyperframes feedback` CLI command and the post-render agent hint already exist, but no skill told agents to act on it — so the feedback channel is starved (agents see a dim stdout line and move on). Add the instruction to the three paths agents actually read in the hyperframes-cli skill: workflow step 8, an Agent Conventions bullet, and a dedicated `feedback` subsection in the preview-render reference.
…struction # Conflicts: # skills-manifest.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The feedback dashboard shows only ~15 responses since the feature shipped. Root cause isn't the CLI —
hyperframes feedback --rating --commentexists, and the post-render flow already prints an agent hint when it detects an agent runtime. But no skill ever told agents to act on it, so agents see a dim stdout line in the render output and move on. The agent feedback channel — where most renders actually happen — is silent by default.What
Add the feedback instruction to the three paths agents actually read in the
hyperframes-cliskill:preview-render.md### feedbacksubsection — full usage detail with a realistic example comment.skills-manifest.jsonregenerated by the pre-commit hook.Note
This lives in
skills/source. Agents run against the installed skill set (pulled oninit), so it reaches them once merged and served by the skills registry. No code change — the CLI plumbing already works; this just gives agents the standing order to use it.