Factory Triage
mastra-ai/mastra
Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage
Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports.
MITAuto-check passed
Install Factory Collect
$ npx skills add BuilderIO/skills --skill factory-collect -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuilderIO/skills factory-collect --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/factory-collect .claude/skills/factory-collect && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "factory-collect" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-collect into .claude/skills/factory-collect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-collect", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BuilderIO/skills/tree/main/skills/factory-collectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BuilderIO/skills --skill factory-collect -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuilderIO/skills factory-collect --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/factory-collect .agents/skills/factory-collect && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "factory-collect" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-collect into .agents/skills/factory-collect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-collect", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill factory-collect -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuilderIO/skills factory-collect --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/factory-collect .cursor/skills/factory-collect && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "factory-collect" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-collect into .cursor/skills/factory-collect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-collect", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BuilderIO/skills.git --path skills/factory-collect--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BuilderIO/skills --skill factory-collect -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuilderIO/skills factory-collect --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/factory-collect .gemini/skills/factory-collect && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "factory-collect" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-collect into .gemini/skills/factory-collect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-collect", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BuilderIO/skills factory-collectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BuilderIO/skills --skill factory-collect -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/factory-collect .github/skills/factory-collect && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "factory-collect" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-collect into .github/skills/factory-collect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-collect", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill factory-collect -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BuilderIO/skills factory-collect --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/factory-collect .opencode/skills/factory-collect && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "factory-collect" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-collect into .opencode/skills/factory-collect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-collect", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
factory-collect- GitHub stars
- 4.5k
- Token cost
- ~807 tokens
- SKILL.md length
- 402 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports.
- Scanning configured signal sources and applying separate fix
- SKILL.md covers Collect and verify coverage, Triage and act and Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Factory Collect is an agent skill from BuilderIO/skills. Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is MIT.
When your agent uses it
- Scanning configured signal sources and applying separate fix
Example prompts
- “/factory-collect”
What it can do on your machine
Read from SKILL.md and the folder at commit 530d9ee. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Factory Collect loads about 807 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 402 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from BuilderIO/skills at commit 530d9ee, republished under its MIT licence (© BuilderIO). 402 words, ~807 tokens.
Download SKILL.mdSave it as
.claude/skills/factory-collect/SKILL.md (or your agent's skills folder).- name
- factory-collect
- description
- Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.
- installer-group
- factory
Factory Collect
Read .agent-factory/config.yaml and apply the optional
skill_prompts.factory-collect entry as additional project guidance. Collect
only the sources named by workflows.collect.sources. For repeated patterns
across time or sources, use factory-lookback.
Collect and verify coverage
- Resolve each source ID to the connected read tool and exact scope recorded in the config. Sources may include support or chat feedback, issue trackers, product analytics or telemetry, and error monitoring.
- Use the configured time range or source cursor. Follow pagination to the end and record the filters, range, cursor/page coverage, and source counts.
- Keep
empty,unavailable, andtruncateddistinct. A missing connector, partial page, or failed query is not an empty source. - Preserve source links, timestamps, useful version or environment dimensions, and relevant discussion. Avoid copying secrets or unnecessary personal data.
- For telemetry, report the metric and aggregation window. Distinguish event counts from unique users or affected sessions unless the source provides a reliable identity definition.
Triage and act
Classify each item as a verified defect, repeated symptom, feature request, subjective feedback, duplicate, out of scope, or needing more evidence. Group related reports while retaining each source record and reporter.
Implement only when workflows.collect.implement allows the change and the
repository is in scope. Stop for configured risk conditions, unclear product
intent, or evidence that cannot be reproduced. Verify the changed behavior
with the configured checks and a representative reproduction.
| Action | Gate |
|---|---|
| Reply | When missing information blocks triage or verification, ask one targeted question only if workflows.collect.reply allows it; follow configured tone and guidance. never means no public reply. |
| Close or mark fixed | Follow workflows.collect.close and wait for its proof point. Do not imply an unverified release. |
| Publish, approve, merge, or deploy | Requires its own workflow authorization; collection does not grant it. |
Show full SKILL.md (115 more words)Show less
When an item needs more information, keep it unresolved and retain the source
thread link and the exact question. If replies are disabled, include that
question in the report for a person to send. On later collection runs, check
whether an answer arrived. Re-triage the original report together with the
answer, then apply the implementation and verification rules again; receiving
an answer does not itself authorize a fix or external action. Use
factory-lookback to compare these follow-ups with prior reports and fixes.
Report
Summarize coverage by source, including unavailable or truncated reads. For each item or related group, give its links, classification, evidence, disposition, checks, any external action, and the exact human decision still needed.
© BuilderIO, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/factory-collect of BuilderIO/skills.
Open the folder on GitHubat commit 530d9ee
Compare with similar skills
Factory Collect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Factory Collect this skillBuilderIO/skills | 4.5k | — | ~807 | Automated safety check: Pass | MIT | |
| Factory Triagemastra-ai/mastra | 29k | — | ~4.5k | Automated safety check: Pass | Custom licence | |
| Omh Feedback Triagerlaope/oh-my-hermes | 3.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Triaging Issuespytorch/pytorch | 104k | — | ~4.2k | Automated safety check: Pass | Custom licence | |
| Sentry Triage FeedbackisHarryh/Ark-Pets | 1.1k | — | ~2.1k | Automated safety check: Pass | GPL-3.0 | |
| Issue Triagepaperclipai/paperclip | 98k | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Omh Feedback Triage
rlaope/oh-my-hermes
[omh] Unsorted customer feedback and bug reports: cluster customer signals and choose the next workflow.
Triaging Issues
pytorch/pytorch
Triages GitHub issues by routing to oncall teams, applying labels, and closing questions.
Sentry Triage Feedback
isHarryh/Ark-Pets
A skill your agent uses when the user asks to triage user feedback collected on Sentry.
Issue Triage
paperclipai/paperclip
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
Customer Feedback Triage
borghei/Claude-Skills
Inbound customer-feedback triage system. An agent skill from borghei/Claude-Skills.
More from BuilderIO/skills
All 25 skills in this repoAgent Watchdog
BuilderIO/skills
A skill your agent uses when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log…
Plan Arbiter
BuilderIO/skills
A skill your agent uses when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed…
Plow Ahead
BuilderIO/skills
A skill your agent uses when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done"…
Read The Damn Docs
BuilderIO/skills
A skill your agent uses when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs…
Stay Within Limits
BuilderIO/skills
A skill your agent uses when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window…
Efficient Fable
BuilderIO/skills
A skill your agent uses when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy…
Questions about Factory Collect
What does Factory Collect do?
Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Factory Collect is an agent skill from BuilderIO/skills. Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports.
When should I use Factory Collect?
Factory Collect fits situations like: scanning configured signal sources and applying separate fix.
How do I install Factory Collect in Claude Code?
Run `npx skills add BuilderIO/skills --skill factory-collect -a claude-code`. Or copy the skill folder (skills/factory-collect in BuilderIO/skills) into .claude/skills/factory-collect in your project. Claude Code loads it when a task matches its description.
How do I install Factory Collect in Codex?
Run `npx skills add BuilderIO/skills --skill factory-collect -a codex`. Or copy the skill folder (skills/factory-collect in BuilderIO/skills) into .agents/skills/factory-collect in your project. Codex loads it when a task matches its description.
Can I use Factory Collect in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BuilderIO/skills --skill factory-collect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/factory-collect, .gemini/skills/factory-collect, .github/skills/factory-collect and .opencode/skills/factory-collect in your project.
What does Factory Collect need to run?
SKILL.md names no scripts, command-line tools or credentials: Factory Collect is instructions for the agent only.
Does Factory Collect access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Factory Collect safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Factory Collect use?
Factory Collect is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Factory Collect use?
About 807 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Factory Collect?
Skills that share tags, products or a category with Factory Collect: Factory Triage (mastra-ai/mastra, 29k stars), Omh Feedback Triage (rlaope/oh-my-hermes, 3.2k stars), Triaging Issues (pytorch/pytorch, 104k stars) and Sentry Triage Feedback (isHarryh/Ark-Pets, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Factory Collect?
BuilderIO (a GitHub organization) maintains it in BuilderIO/skills, which has 4,528 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 7, 2026.
Source: BuilderIO/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.