Run any Skill in Manus with one click

setup

Stars2

Forks0

UpdatedJune 13, 2026 at 15:17

One-time setup of YOUR lens memory loop on Claude Code — your foundry where the SessionEnd hook queues lens sessions, /lens:retro mines them, and /lens:new grows your collection. Use when the user runs /lens:setup, or when a foundry-dependent skill (retro, new) finds no config. Claude Code only — the loop is not supported on Cowork.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Tiltely

Tiltely/lens

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	setup
description	One-time setup of YOUR lens memory loop on Claude Code — your foundry where the SessionEnd hook queues lens sessions, /lens:retro mines them, and /lens:new grows your collection. Use when the user runs /lens:setup, or when a foundry-dependent skill (retro, new) finds no config. Claude Code only — the loop is not supported on Cowork.

Lens Setup (Claude Code)

The memory loop — a SessionEnd hook that queues lens sessions, /lens:retro to mine them, /lens:new to grow your collection — is a Claude Code feature. Setup creates your foundry and wires it up. Without setup, all bundled lenses and /lens:socratic still work; setup only adds the loop.

On Claude Cowork: not supported — stop here

If you detect Cowork, do NOT set up a foundry. The memory loop does not run on Cowork: its sandbox spawns the CLI with --setting-sources user, so plugin-provided hooks (the SessionEnd queue) never fire, and the VM home is ephemeral. Tell the user plainly: on Cowork, just use the lenses and /lens:socratic directly — they work fully. Run /lens:setup on Claude Code to enable the loop there. Then stop — no foundry, no config, no folder grant.

On Claude Code: set up the loop

The foundry holds PERSONAL session data (session IDs, project/transcript paths, mined observations) — never commit it to git. Use a private, persistent, non-tracked folder.

Choose the foundry location — default ~/.claude/lens-foundry/; any non-git folder is fine, but NEVER inside a git working tree. Create it with empty pending-retros.jsonl and processed-retros.jsonl, an observations.md with a one-line header ("Cross-project learnings mined by /lens:retro; append-only"), a registry.md (your lenses — same columns as ${CLAUDE_PLUGIN_ROOT}/core/registry.md, starting empty), and an empty lenses/ dir (where /lens:new writes your global lenses; /lens:socratic reads them inline).
Write the config at ~/.claude/lens.json (show the user first):
```
{ "foundry": "<foundry path>" }
```
Hand the user the cross-cwd permission rule so retro/hook writes never prompt from other projects' sessions. Do NOT edit ~/.claude/settings.json yourself — permission-widening by an agent is blocked by the auto-mode classifier by design. Print a paste-ready node -e one-liner the USER runs, merging into their settings and preserving everything else:
```
permissions.additionalDirectories += "<foundry path>"
permissions.allow += [ "Edit(//<foundry path>/**)", "Write(//<foundry path>/**)" ]
```
Optional — without it the user just gets a one-time prompt on the first cross-project foundry write.
Verify: run ${CLAUDE_PLUGIN_ROOT}/scripts/queue-retro.sh with no stdin — it must exit 0 silently. Confirm the config parses (cat it back).
Tell the user: the SessionEnd hook now queues lens-using sessions; run /lens:retro to process them, /lens:new to grow your collection (used via /lens:socratic — not as separate slash commands).

More from this repository

same repository

socratic

Tiltely/lens

Use when starting any non-trivial feature, issue, or objective — BEFORE designing or coding — and again AFTER implementing, to audit it. Design mode runs iterative Socratic discovery (caveats, rabbit holes, blast radius), then plans and chains the right lenses. Audit mode re-runs the session's lens plan against the implemented code and verifies it against the dossier's recorded decisions. Trigger phrases - "let's build", "add feature", "how should we approach", "audit what we built", "review the implementation".

2026-06-162

observability

Tiltely/lens

The Lens of Observability — Socratic battery over operational recovery and visibility for money flows, state machines, webhooks, and background jobs. Use for anything where a lost external event or a stalled multi-step flow can strand a user (payments, webhooks, onboarding funnels, queues, crons). Modes - design (questions to you) and audit (questions to the code).

2026-06-152

security

Tiltely/lens

The Lens of Security — Socratic question battery over sessions, auth, tokens, secrets, and authorization. Use for any feature touching login, tokens, payments, user data, webhooks, file uploads, or anything an attacker would love. Modes - design (questions to the user) and audit (questions to the code).

2026-06-152

retro

Tiltely/lens

The memory loop. Use when closing significant work or weekly — processes queued lens sessions, mines them for patterns, proposes new lenses / lens updates / CLAUDE.md diffs, and writes approved observations to the foundry ledger. Also accepts an explicit transcript path or session_id as argument.

2026-06-132

adversary

Tiltely/lens

The Lens of the Adversary — red-teams a PLAN before you commit to it. Tries to refute it, names the weakest decision and the unexamined assumption, re-checks the four excavations against the plan. Runs as the MANDATORY final step of /lens:socratic, or standalone (/lens:adversary) on any plan, diff, or design. A meta-lens — it critiques the plan, not a domain.

2026-06-132

new

Tiltely/lens

Scaffold a new lens for this plugin. Use when /lens:retro proposed a lens, or a recurring theme has no lens. Takes a lens name (kebab-case) and a one-line purpose.

2026-06-132

name	setup
description	One-time setup of YOUR lens memory loop on Claude Code — your foundry where the SessionEnd hook queues lens sessions, /lens:retro mines them, and /lens:new grows your collection. Use when the user runs /lens:setup, or when a foundry-dependent skill (retro, new) finds no config. Claude Code only — the loop is not supported on Cowork.

Lens Setup (Claude Code)

On Claude Cowork: not supported — stop here

On Claude Code: set up the loop

The foundry holds PERSONAL session data (session IDs, project/transcript paths, mined observations) — never commit it to git. Use a private, persistent, non-tracked folder.

Choose the foundry location — default ~/.claude/lens-foundry/; any non-git folder is fine, but NEVER inside a git working tree. Create it with empty pending-retros.jsonl and processed-retros.jsonl, an observations.md with a one-line header ("Cross-project learnings mined by /lens:retro; append-only"), a registry.md (your lenses — same columns as ${CLAUDE_PLUGIN_ROOT}/core/registry.md, starting empty), and an empty lenses/ dir (where /lens:new writes your global lenses; /lens:socratic reads them inline).
Write the config at ~/.claude/lens.json (show the user first):
```
{ "foundry": "<foundry path>" }
```
Hand the user the cross-cwd permission rule so retro/hook writes never prompt from other projects' sessions. Do NOT edit ~/.claude/settings.json yourself — permission-widening by an agent is blocked by the auto-mode classifier by design. Print a paste-ready node -e one-liner the USER runs, merging into their settings and preserving everything else:
```
permissions.additionalDirectories += "<foundry path>"
permissions.allow += [ "Edit(//<foundry path>/**)", "Write(//<foundry path>/**)" ]
```
Optional — without it the user just gets a one-time prompt on the first cross-project foundry write.
Verify: run ${CLAUDE_PLUGIN_ROOT}/scripts/queue-retro.sh with no stdin — it must exit 0 silently. Confirm the config parses (cat it back).
Tell the user: the SessionEnd hook now queues lens-using sessions; run /lens:retro to process them, /lens:new to grow your collection (used via /lens:socratic — not as separate slash commands).