OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes.
MITAuto-check passed
Install Factory Lookback
$ npx skills add BuilderIO/skills --skill factory-lookback -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuilderIO/skills factory-lookback --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-lookback .claude/skills/factory-lookback && 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-lookback" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-lookback into .claude/skills/factory-lookback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-lookback", 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-lookbackType 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-lookback -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuilderIO/skills factory-lookback --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-lookback .agents/skills/factory-lookback && 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-lookback" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-lookback into .agents/skills/factory-lookback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-lookback", 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-lookback -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuilderIO/skills factory-lookback --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-lookback .cursor/skills/factory-lookback && 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-lookback" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-lookback into .cursor/skills/factory-lookback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-lookback", 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-lookback--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-lookback -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuilderIO/skills factory-lookback --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-lookback .gemini/skills/factory-lookback && 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-lookback" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-lookback into .gemini/skills/factory-lookback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-lookback", 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-lookbackInstalls 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-lookback -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-lookback .github/skills/factory-lookback && 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-lookback" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-lookback into .github/skills/factory-lookback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-lookback", 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-lookback -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-lookback --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-lookback .opencode/skills/factory-lookback && 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-lookback" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/factory-lookback into .opencode/skills/factory-lookback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "factory-lookback", 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-lookback- GitHub stars
- 4.5k
- Token cost
- ~1k tokens
- SKILL.md length
- 541 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes.
- Works in 4 steps: Confirm the configured sources, scope,… → Enumerate the full configured range,… → Include relevant feedback, analytics or… → …
- Requested cross-source lookbacks
- SKILL.md covers Build a bounded evidence set, Find the systemic cause, Change and verify and Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Factory Lookback is an agent skill from BuilderIO/skills. 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.
Its SKILL.md is about 1k 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
- Requested cross-source lookbacks
- Not routine single-item intake
Example prompts
- “/factory-lookback”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Confirm the configured sources, scope, time window, comparison period, and
- Enumerate the full configured range, follow every page or cursor, and record
- Include relevant feedback, analytics or telemetry, runtime errors,
- Cluster records by underlying symptom and affected boundary, not wording
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 Lookback loads about 1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 541 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). 541 words, ~1,018 tokens.
Download SKILL.mdSave it as
.claude/skills/factory-lookback/SKILL.md (or your agent's skills folder).- name
- factory-lookback
- 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.
- installer-group
- factory
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.
Show full SKILL.md (200 more words)Show less
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.
© 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-lookback of BuilderIO/skills.
Open the folder on GitHubat commit 530d9ee
Compare with similar skills
Factory Lookback 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 Lookback this skillBuilderIO/skills | 4.5k | — | ~1k | Automated safety check: Pass | MIT | |
| OmniRoute Audit and Policy CLIdiegosouzapw/OmniRoute | 74k | — | ~733 | Automated safety check: Pass | MIT | |
| Feedbackcodewhale-hq/Codewhale | 41k | — | ~272 | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 274k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
Feedback
codewhale-hq/Codewhale
Report a Codewhale bug or idea as a GitHub issue. An agent skill from codewhale-hq/Codewhale.
Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
Geo Audit
sickn33/agentic-awesome-skills
Full website GEO+SEO audit with parallel subagent delegation.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
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 Lookback
What does Factory Lookback do?
Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Factory Lookback is an agent skill from BuilderIO/skills. Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes.
When should I use Factory Lookback?
Factory Lookback fits situations like: requested cross-source lookbacks; not routine single-item intake.
How do I install Factory Lookback in Claude Code?
Run `npx skills add BuilderIO/skills --skill factory-lookback -a claude-code`. Or copy the skill folder (skills/factory-lookback in BuilderIO/skills) into .claude/skills/factory-lookback in your project. Claude Code loads it when a task matches its description.
How do I install Factory Lookback in Codex?
Run `npx skills add BuilderIO/skills --skill factory-lookback -a codex`. Or copy the skill folder (skills/factory-lookback in BuilderIO/skills) into .agents/skills/factory-lookback in your project. Codex loads it when a task matches its description.
Can I use Factory Lookback 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-lookback -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-lookback, .gemini/skills/factory-lookback, .github/skills/factory-lookback and .opencode/skills/factory-lookback in your project.
What does Factory Lookback need to run?
SKILL.md names no scripts, command-line tools or credentials: Factory Lookback is instructions for the agent only.
Does Factory Lookback 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 Lookback 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 Lookback use?
Factory Lookback 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 Lookback use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Lookback?
Skills that share tags, products or a category with Factory Lookback: OmniRoute Audit and Policy CLI (diegosouzapw/OmniRoute, 74k stars), Feedback (codewhale-hq/Codewhale, 41k stars), Production Audit (affaan-m/ECC, 274k stars) and Aims Audit (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Factory Lookback?
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.