factory-human-digest
Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
Install / Use
npx skills add BuilderIO/skills --skill factory-human-digestInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of factory-human-digest
factory-human-digest scores 82/100 on our quality scale, 2268th of 2,780 Automation skills we index.
Its SKILL.md is 3.8 KB long, split into 5 sections and no code examples: a solid amount of guidance for an agent.
With 4,394 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so factory-human-digest is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
factory-human-digest compared with similar skills
All 4 of these similar skills score higher than factory-human-digest; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| factory-human-digest (this skill)by BuilderIO | 82 | 4.4k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install factory-human-digest?
- Run
npx skills add BuilderIO/skills --skill factory-human-digest. The install tabs above show the steps for each supported agent. - Which AI agents does factory-human-digest work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is factory-human-digest safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is factory-human-digest still maintained?
- The repository was last updated about 2 months ago, so factory-human-digest is actively maintained.
Skill content
View source on GitHubname: factory-human-digest installer-group: factory description: >- Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
Factory Human Digest
Start with the Factory guide for workflow setup and configuration.
Read .agent-factory/config.yaml and apply the optional
skill_prompts.factory-human-digest entry as additional project guidance.
Inspect only the repositories and sources it authorizes.
Choose the scope
For a manual run with no narrower request or workflow settings, include all
configured source categories, use the last 7 days, and report at balanced
granularity. A user can narrow or expand the request in ordinary language, for
example, “PRs only, last 30 days, detailed” or “everything from this week, brief.”
Use configured repository and source boundaries even when the requested time
window or category changes. For scheduled runs, use
workflows.human-digest from the config.
Categories can include pull requests, issues, feedback, errors, telemetry, and stalled or failed delivery work. A category filter selects records to inspect; it does not expand access to another project or integration.
Find items that need a person
Read configured sources and repositories completely for the selected window. Follow pagination and record the actual dates, filters, counts, and any source that was unavailable or truncated. Include items held outside the normal agent-handled flows, such as:
- pull requests waiting for human review, approval, a merge decision, or product judgment;
- issues, feedback, or errors held for missing context, unclear intent, risk, conflicting evidence, or a decision outside the configured automation rules;
- new answers to information requests that have not yet been re-triaged;
- recurring incidents, UX concerns, or delivery work that stopped without a verified resolution or safe authorized next step.
Exclude work that has a verified terminal outcome unless it reopened, recurred, or received new information during the window. A label or agent summary alone does not prove an item is resolved. If the source cannot distinguish pending from resolved, report that uncertainty instead of guessing.
Group patterns and preserve evidence
Group related items by the underlying user impact or failure pattern, not by similar words alone. For each group, preserve the date range, count of distinct records, source links, representative evidence, and the human decision needed. Separate event volume from affected people or sessions unless the source has a reliable identity definition. Keep unrelated reports separate even when one summary would be shorter.
Use the configured granularity, or balanced by default:
- Brief: top groups, why each needs a person, and links to the source items.
- Balanced: grouped summaries, representative evidence, and a linked list of each item needing a decision.
- Detailed: one entry per item with relevant context, prior handling, evidence, and the exact decision or next step.
Report; do not take the actions
Start with coverage: window, categories, repositories, sources, filters, and pagination status. Then report recurring themes and the decision queue. For each entry include links, why the normal flow did not handle it, prior replies or dispositions, the decision required, and an owner or due date only when the source provides one.
This workflow is read-only. Do not reply, approve, merge, assign, close, change status, or notify people from the digest. Route any requested action through its owning Factory workflow and its separate configured policy. Missing or partial source data must remain visible in the report; it is never evidence of an empty queue.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
