Factory Collect

OrganizationPopular

BuilderIO

factory-collect

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.

Overview

Publisher	BuilderIO
Repository	`skills`
Skill name	`factory-collect`
Stars	4.6K
Forks	231
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by BuilderIO on GitHub. Read the source before you install it.

Installation

Install the Factory Collect AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/BuilderIO/skills/tree/main/skills/factory-collect
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/BuilderIO/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/factory-collect .claude/skills/factory-collect

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Factory Collect in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Factory Collect on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Factory Collect is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

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.

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.

Frequently asked questions

What does the Factory Collect AI skill do?

Why use Factory Collect on TypingMind?

Because you install it once and use it with any model. Factory Collect is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Factory Collect in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/BuilderIO/skills/tree/main/skills/factory-collect. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Factory Collect?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Factory Collect?

As many as you like. As long as a model supports skills, you can use Factory Collect with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Factory Collect AI skill free?

Yes. It is published on GitHub by BuilderIO under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Deployment Patterns

affaan-m

CommunityPopular

Flujos de trabajo de despliegue, patrones de pipeline CI/CD, contenedorización Docker, health checks, estrategias de rollback y listas de verificación de preparación para producción de aplicaciones…

Docker Patterns

Patrones de Docker y Docker Compose para desarrollo local, seguridad de contenedores, networking, estrategias de volúmenes y orquestación de múltiples servicios.

Architecture Decision Records

affaan-m

CommunityPopular

コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。

Automation Audit Ops

ECC用の証拠ベースの自動化インベントリとオーバーラップ監査ワークフロー。ユーザーがどのジョブ、フック、コネクタ、MCPサーバー、またはラッパーがライブか、壊れているか、冗長であるか、修正前に不足しているかを知りたい場合に使用します。

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Factory Collect

Collect and verify coverage

Triage and act

Report

Frequently asked questions

Related AI Skills

Set up your own AI workspace now