AutoGineer
Generated banner for Factory Collect
Generated logo for Factory Collect

Factory Collect

Builder.ioOfficialPublished by Builder.io

  • Skill
  • Workflow
  • Automation and integrations
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Builder.io

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Factory Collect is a structured workflow designed to aggregate data from various product feedback channels, telemetry streams, and error monitoring tools. It provides a systematic approach to reading, verifying, and triaging incoming signals based on project-specific configurations. The skill emphasizes clear categorization of reports, adherence to defined implementation gates, and maintaining traceability between source data and subsequent actions.

What it does

  • Resolves and reads data from configured feedback, telemetry, and issue tracking sources.
  • Verifies data coverage by tracking filters, ranges, and source status.
  • Classifies incoming items into categories like defects, feature requests, or duplicates.
  • Groups related reports while maintaining original source context and metadata.
  • Applies conditional logic for replying, closing, or marking items as fixed based on project rules.
  • Generates summary reports detailing source coverage, item disposition, and pending human decisions.

When to use it

  • When you need to centralize feedback and error reports from multiple disparate sources.
  • When you want to automate the initial triage and classification of incoming product signals.
  • When you need to ensure that automated actions like closing issues or replying to users follow strict project guidelines.
  • When you need to track the status of reports that require additional information from users.

Advantages

  • Reduces manual effort in aggregating and categorizing product feedback.
  • Ensures consistent handling of reports through configurable triage rules.
  • Maintains clear audit trails by linking actions back to original source records.
  • Prevents unauthorized actions by enforcing strict implementation gates.

Usage examples

“Run the factory-collect workflow to scan my configured issue trackers and feedback channels.”
The agent will read the sources defined in the configuration, categorize the new items, and provide a summary report of the findings and any required human actions.
“Check for updates on previously unresolved feedback items using factory-collect.”
The agent will re-scan the sources, check for new information on pending items, and re-triage them based on the updated data.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/builderio/factory-collect/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip factory-collect.zip -d .agents/skills

Documentation by Builder.io

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, and truncated distinct. 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.

ActionGate
ReplyWhen 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 fixedFollow workflows.collect.close and wait for its proof point. Do not imply an unverified release.
Publish, approve, merge, or deployRequires its own workflow authorization; collection does not grant it.

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.

Files

LICENSE

MIT License

Copyright (c) 2026 Builder.io

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Builder.io
Publisher
Builder.io (Official)
Source
BuilderIO/skills · skills/factory-collect · commit f4f10b8
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Builder.io.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download factory-collect.zip