factory-lookback
Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.
Install / Use
npx skills add BuilderIO/skills --skill factory-lookbackInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of factory-lookback
factory-lookback scores 82/100 on our quality scale, 2269th of 2,780 Automation skills we index.
Its SKILL.md is 4.0 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-lookback 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-lookback compared with similar skills
All 4 of these similar skills score higher than factory-lookback; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| factory-lookback (this skill)by BuilderIO | 82 | 4.4k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d 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-lookback?
- Run
npx skills add BuilderIO/skills --skill factory-lookback. The install tabs above show the steps for each supported agent. - Which AI agents does factory-lookback 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-lookback 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-lookback still maintained?
- The repository was last updated about 2 months ago, so factory-lookback is actively maintained.
Skill content
View source on GitHubname: factory-lookback installer-group: factory description: >- Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.
Factory Lookback
Read .agent-factory/config.yaml and apply the optional
skill_prompts.factory-lookback entry as additional project guidance. Use this
workflow when asked to look back across a bounded period or when an enabled
workflows.lookback automation runs. Its purpose is to find patterns that
normal item-by-item flows keep missing or fixing only temporarily.
Build a bounded evidence set
- Confirm the configured sources, scope, time window, comparison period, and output policy before querying. Use only connected sources the host can read.
- Enumerate the full configured range, follow every page or cursor, and record source filters, dates, counts, and unavailable or truncated sources. Do not report a complete lookback when coverage is partial.
- Include relevant feedback, analytics or telemetry, runtime errors, recurring CI or review failures, repeated recovery attempts, replies to earlier information requests, and prior fixes marked shipped or verified when those records are available.
- Cluster records by underlying symptom and affected boundary, not wording alone. Keep event counts, affected users or sessions, time range, versions, and distinct source links separate; do not infer identity or impact from unstable identifiers.
Find the systemic cause
For each recurring cluster, trace representative reports to their original source and inspect prior dispositions, commits, tests, and release evidence. Check whether the symptom recurred after a claimed fix, appeared through a sibling caller, or escaped because the normal workflow lacked a signal, owner, verification step, or recovery path.
For a report previously held for more information, inspect the full source thread for new replies. Re-triage the original report with the new details and check whether the normal fix flow now has enough evidence to proceed. Keep the item open when the answer is still incomplete; do not treat a reply as a fix or as permission for another action.
Reproduce a representative current case when possible. Trace related callers and surfaces to the shared boundary that can explain the evidence. Prefer one verified correction at that boundary over a pile of caller-specific patches. Separate confirmed causes from hypotheses, and state what evidence would disprove each proposed explanation.
Change and verify
Use workflows.lookback.implement to decide whether to recommend only, prepare
a fix, or publish an authorized change. A recurring pattern is evidence for
investigation, not automatic permission to edit code or take an external
action. Keep reply, issue closure, PR approval, merge, deployment, and
notification under their own configured policies.
When implementation is allowed, make the smallest systemic fix that addresses the confirmed cause. Add or update a regression check at the boundary, exercise the representative failure and relevant sibling paths, and inspect the same signals again after the fix. A test, merge, or “fixed” label alone does not prove that the live recurrence stopped.
Report
For each pattern, report:
- the source links, date range, query coverage, counts, and impact evidence;
- prior fixes or dispositions and whether the symptom returned;
- information requests, answers received, and whether they changed the evidence or next step;
- confirmed cause, alternatives still uncertain, and the shared boundary;
- recommended or completed systemic change, regression proof, and remaining rollout or live-verification work;
- independent reply, close, publish, approval, merge, deployment, and notify decisions, plus any exact human decision required.
Do not treat unavailable telemetry or an incomplete history as evidence that a pattern does not exist.
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.
