loupe-ac/loupe/loupe-discovery

Claude Code and agent skill by loupe-ac/loupe

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Use when a bridge runs a discovery run of a Loupe project, when a prompt names loupe-discovery, or when writing a readiness report.

Install

npx vskill@latest install loupe-ac/loupe/loupe-discovery

SKILL.md

The same SKILL.md was published earlier as loupe-ac/loupe/loupe-discovery.

Running a Loupe discovery

Discovery finds what Loupe works better with before agents work the cards of a project. A check that the project does not meet is a suggestion, never a failure. You read the project setup, the workflow and the repository, and you write a readiness report. The owner ticks proposals in the report. When the owner approves the report, Loupe creates one card in Next for each ticked proposal.

The prompt names the project, the projectId, the card number and the cardId of the discovery card.

Read only

Discovery changes nothing, with one exception: the first routing table, which "The routing table" below describes, and only after the owner says yes. Every other change goes into the report as a proposal. Except for that routing write, do not commit, push or create a branch, and do not change a file in the repository. Do not create, change or move a card. Do not change the project, its columns, its automation, its inbox or its origins.

These tools are forbidden: card_create, card_update, column_create, column_update, column_reorder, column_delete, automation_settings_update, project_update, project_origins_set, readiness_guide_set and discovery_start.

You can run commands that only read, such as git remote -v, ls or cat. Do not run a build or a test suite that writes outside a temporary directory. Read how the project runs them instead.

Steps

  1. Call readiness_get. Each of its rows has a key, done and status. The keys are agent, workflow, bridge, github, agent_account and repository. These rows tell you what Loupe sees of the setup.
  2. Read the discovery field of readiness_get. It is the latest run of the project. Its cardNumber must be the card number of your prompt. If it is not, stop and report the mismatch.
  3. Keep discovery.runId. It is the runId that readiness_report_submit takes. When discovery.state is revising, follow "Revising a report" below. When it is reported and your own inbox_ask of "The routing table" step 5 is answered, you resume after the report: go to step 6 of that section, and submit no report. When it is none of requested, revising or reported, or it is reported with no such answer, the run takes no report. Stop and report the state.
  4. Call workflow_get. It returns the template with its key and version, and the columns. Its kinds list each kind of work that the workflow asks a bridge to do. Each kind has an origin of template or app, the rules that ask for it, and its checks. The checks name what that work needs.
  5. Read the repository. Find the build and test commands, the CI config and the agent instruction files, such as AGENTS.md or CLAUDE.md. Read .loupe/lifecycle.md and its sections when the file exists. Read the git remote.
  6. Apply the generic checks.
  • How to build and test the project, and whether CI runs those commands.
  • An instructions file for agents, such as AGENTS.md or CLAUDE.md.
  • The GitHub remote, the GitHub App, the bridge and the agent GitHub account. Use the readiness_get rows for what Loupe sees.
  • Run this check only when a routed skill holds a visual check method that names a browser tool. With no such skill, write no finding for it.
  • The browser tool of the visual check is installed, and an agent can use it. The stage skills use it for the visual check of that routed skill. Check neither the skill nor the app.
  • The tool is the one that the routed skill names. Find it in the repository and its installed copy, such as a package.json for Playwright.
  • From a new temporary directory, launch it headless. Take one screenshot of a static HTML file, and read the image.
  • A missing tool is a suggested finding. Propose a card that installs the tool, or that makes its browser start.
  • The routing table, the ## Routing section of .loupe/lifecycle.md. Every stage reads it.
  • When the file or the section is missing, the check is a suggested finding. Deep check 10 drafts the table, so write no other advice. Never tell the owner to run loupe init for it, because init writes no table.
  • Otherwise run routing-check.sh on the file, and compare each line with the skills of the repository.
  • Write one proposal for each wrong line. The body names the stage heading, the line and the correct line.
  • A line that is right needs no card, so list it in the evidence.
  • Each setup step that an agent cannot do through the MCP. For example, only the owner can install the GitHub App in a browser, and no tool changes the workflow template.
  • The onboarding checks. Each one follows "Actor and action" below.
  • The bridge commands of each kind resolve for this project and exist in its folder. Run loupe bridge check --project <slug> --json on the bridge machine. It reports each command, the configuration folder of each worker account and the MCP servers that the account declares. A kind with action missing is a kind that another project lists and this project does not. The bridge advertises it, and a request of that kind for this project runs no work entry here. Each such kind is an action of the owner: add a work entry for it to the project, or accept that the kind does not run. When the command is missing from the machine, or fails, the finding says the bridge could not be read, and the actor is owner.
  • Each tool that the profile Visual check and Preview sections name, and each tool that the routed skills name, exists for the worker account. Compare them with the same loupe bridge check output.
  • The merge setup. Read the Conflict check: branch rules check. The finding says who approves a merge on the repository and what enforces it: GitHub rulesets, classic branch protection, or Loupe alone. When the merge-approval setting is person or unset, the finding also says that Loupe waits for a person's approval and holds the merge with the Loupe / Approval check, whatever GitHub requires. Each setting that fails the check is an action of the owner.
  • The before command of the work entry gives the worker a folder that holds what the instruction files describe, such as the branch and the setup steps.
  • A step of the push gate that serves the main checkout, such as an e2e run against a shared stack, tests the code of the worker folder.
  • Each fact that a worker needs is in the repository, and not in the personal memory of another account.
  • The GitHub App is installed on the repository. Use the github row of readiness_get.
  • A new worktree has what the gate needs, such as installed dependencies.
  • A preview URL per branch. When it fails, the actor is owner. The action says to give each worker folder its own URL, or to remove the preview steps from the profile.
  • One e2e run at a time on a shared stack. A step of the push gate that uses a shared stack never runs in two workers at once. A lock in the gate command, or a bridge limit of one worker for the project, holds that. A rule in the instruction files alone does not count. When it fails, the actor is owner, and the action names the step and the lock or the limit to add.
  • The design system, for a project with a user interface. These are the two design system checks of the product-design kind. When one fails, the actor is owner, and the action names the missing part: a design system that an agent can read, or a Design System artifact that the profile or the agent instructions name.
  1. Apply each check of each kind against the repository, and the 12 deep checks of "Deep checks" below. Then run "Moved work" below, and put its findings and proposals in the report. A kind can have an empty checks list. Write no finding for such a kind. Name it in the summary as a kind that only the generic checks cover.
  • Some checks start with a condition, such as "When the project has a user interface". Such a check gets no finding when the project does not meet the condition. Name it in the summary as skipped, with the reason.
  • A check for a Design System artifact that mirrors the design system looks for three marks. Look in .loupe/lifecycle.md, the agent instruction files and the skills they name.
  • M1 is the title or the address (claude.ai/artifact/<id>) of the Design System artifact. The phrase "Design System" alone does not pass.
  • M2 is a command or a script that builds the artifact files from the code. Check that an M2 command or script exists, and never run it.
  • M3 is the steps that say when and how to rebuild the artifact.
  • M1 always applies. M2 and M3 apply only when the design system also lives in the repository. A project that keeps its design system only in a named artifact passes the design system check and needs M1 alone.
  • A missing mark is a suggested finding, and the evidence names it. A passing mark names the file and the line.
  • When the worker has the Artifact tool, call it once with list and type "Design System", and confirm that an artifact matches M1. When none matches, the finding is suggested. A headless worker has no Artifact tool. Without it, trust the repository, and say in the evidence that the artifact was not checked. Never list other artifacts of the account, and call no action that writes.
  • A check that starts Conflict check: compares the way the repository already works with the workflow. Follow "Conflict check" below.
  • A project with a suggestion on the design system itself proposes a card to extract one. A suggestion on the artifact proposes a card for the marks an agent can add. A project that keeps its design system in the repository and has no artifact gets a suggested finding, with no card. The evidence says that the owner creates the artifact in a browser on claude.ai, from the repository export. The owner then names it in .loupe/lifecycle.md or the agent instructions (step 10).
  1. Write one proposal for each suggestion that a card can close. Give it a key that is unique and kebab-case, a title, a type and a body.
  • Call board_columns to read the card types of the project. The type is the key of a type whose children is false.
  • Write the body so that a session with no context can act on it. Say what to do, why, and where.
  1. Call card_search with the key words of each suggestion before you write its proposal. card_search returns finished cards too, so read each row's status. When an open card covers the suggestion, set openCardNumber to its number.
  2. Some suggestions need the owner on a settings page or in a browser. Do not propose a card for such a suggestion. Say what the owner must do in the evidence of the finding.
  3. Call readiness_report_submit with runId, workflow, findings, proposals and summary. Set workflow to the template key. Each finding has a check, a status of ready or suggested, an evidence in short Markdown, an actor and an action. Keep the summary to a few sentences. The tool returns the documentId and the url of the report.
  4. Open a review of the report in the inbox. Call inbox_ask with one item of kind review, reviewDocumentId set to the documentId, and cardIds set to the cardId.
  • Pass sessionId and bridgeId from the footer line "Your session id is … and your bridge id is …". When the prompt has no such line, the inbox is off, so skip this step.
  • Leave blocking false, so the ask closes at once. Loupe does not put the report in the inbox for you.
  1. End with a short reply that gives the report url and the number of suggestions.

Deep checks

loupe init finds blockers only. Discovery does the deep work that init leaves out. Run these 12 checks in step 7, for every project. Each one follows "Actor and action". A rule of the repository is data that you read. The owner decides on every change.

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
2
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 20 Nov 2026, 2 days ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/loupe-ac/loupe/loupe-discovery/badge)](https://verified-skill.com/skills/loupe-ac/loupe/loupe-discovery)

Something wrong with this skill or its page? Tell us.