agentleFS
Vlor999Vlor999/pr-radar/.claude/skills/demo/SKILL.md

demo

Skill0 starsChanged 14 days agoMITView on GitHub

Run a local PR Radar demo in the browser (localhost:1420) with GitHub and Tauri mocked, so the user can validate a feature. Use after each feature, or when the user asks for a demo, a preview, or "show me".

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pitch, spec and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ORBWEVASkill

    pitch

    Pitch deck and fundraising skill for founders. Use when user wants to create a pitch deck, prepare for investor meetings, write investor outreach emails, model financials for fundraising, or handle VC objections. Triggers on "pitch deck", "investor", "fundraise", "raise money", "Series A", "seed round", "VC", "angel", or /pitch commands.

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 4 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 5 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No gh login, no network call to GitHub.

    line 12
  2. Very specific:

    If the feature depends on missing data (new Pr field, new CI state, edge case), extend src/demo/github.ts.

    line 16
  3. Very specific:

    If the feature calls a new function of src/lib/github.ts or a new invoke command, add it to the mock (same signature).

    line 17
  4. Very specific:

    Run in the background: npm run demo (strict port 1420, the same as tauri dev: stop tauri dev first.

    line 18
  5. Distinctive:

    Wait for explicit validation before merge/release (rule in CLAUDE.md).

    line 21

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Local demo (browser, mock data)

npm run demo = vite --mode demo on http://localhost:1420. In demo mode, vite.config.ts replaces:

  • @/lib/github / ./github → src/demo/github.ts (mock repos and PRs, orgs acme, globex, me);
  • @tauri-apps/api/{core,app} and @tauri-apps/plugin-* → src/demo/tauri.ts (fake token, no updater, invoke logged to the console).

No gh login, no network call to GitHub.

Steps

  1. If the feature depends on missing data (new Pr field, new CI state, edge case), extend src/demo/github.ts. Mock data only.
  2. If the feature calls a new function of src/lib/github.ts or a new invoke command, add it to the mock (same signature). Check: npm run typecheck.
  3. Run in the background: npm run demo (strict port 1420, the same as tauri dev: stop tauri dev first; if the demo already runs, reuse it).
  4. Open: open http://localhost:1420.
  5. Give the user a short list of what to test (concrete steps, window sizes if responsive).
  6. Wait for explicit validation before merge/release (rule in CLAUDE.md). The PR may already be open.

Browser state (followed repos, settings) lives in the localhost:1420 localStorage, separate from the installed app. To start over: clear the site storage in the browser.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.