New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Redlamp Manual

by pdcgomes in pdcgomes/redlamp

The Redlamp User Manual (docs/manual), a dense, book-style PDF for photographers, typeset from Markdown and a print style sheet by Chrome, with its ranges, defaults and shortcuts generated from the…

MPL-2.0Auto-check passedDocuments & Office

Install Redlamp Manual

skills CLI
$ npx skills add pdcgomes/redlamp --skill redlamp-manual -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pdcgomes/redlamp redlamp-manual --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pdcgomes/redlamp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/redlamp-manual .claude/skills/redlamp-manual && rm -rf skills-src

Use ~/.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/

Facts

Skill name
redlamp-manual
GitHub stars
231
Token cost
~2.8k tokens
SKILL.md length
1,591 words
Files
3
Skills in repo
11
Repo updated
First seen
Licence
MPL-2.0

At a glance

The Redlamp User Manual (docs/manual), a dense, book-style PDF for photographers, typeset from Markdown and a print style sheet by Chrome, with its ranges, defaults and shortcuts generated from the…

  • Works in 5 steps: Facts first. Gather the part's facts… → Plan it in book.toml. Give the section a… → Write it by the rules below. Its front… → …
  • Reviewing the user manual
  • SKILL.md covers Where, Build, Writing a section and Figures, plus 4 more sections
  • Calls python, python3 and pip

What it does

Redlamp Manual is an agent skill from pdcgomes/redlamp. The Redlamp User Manual (docs/manual), a dense, book-style PDF for photographers, typeset from Markdown and a print style sheet by Chrome, with its ranges, defaults and shortcuts generated from the app's code. Knows the manual's sources, its Markdown additions, figures and generated tables, the build and its checks, its page design, and how a part is researched and written. Use when writing, editing, building or reviewing the user manual, adding a part, section, figure or table to it, changing its look, or…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `design.md` and `fact-sheet.md`).

It sits in Documents & Office, covering Technical writing and Markdown. The repository describes itself as: A native, open-source RAW photo editor for Mac, iPad and iPhone that feels immediately familiar to Lightroom users. The licence is MPL-2.0.

When your agent uses it

  • Reviewing the user manual
  • Changing its look
  • Bringing it up to date with the app

Example prompts

  • “s code. Knows the manual”
  • “/redlamp-manual”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Facts first. Gather the part's facts from the code into docs/manual/facts/.md, with a path and line for every fact, inferences marked, and…
  2. Plan it in book.toml. Give the section a file. Numbers follow the order: the part's number, then 3.1, 3.2 and so on. A heading's id is the…
  3. Write it by the rules below. Its front matter has deck, one or two sentences that summarise it in italics under the title, and sources…
  4. Build, and look at every page it touches as PNGs, with the checklist.
  5. Commit on your own branch, naming the part (User manual: Part 2, white balance and tone), and update the canvas.

What it can do on your machine

Read from SKILL.md and the folder at commit 9587460. 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

    Shell commands in SKILL.md call:

    • python
    • python3
    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    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

Redlamp Manual loads about 2.8k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 1,591 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~141
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

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 pdcgomes/redlamp at commit 9587460, republished under its MPL-2.0 licence (© pdcgomes). 1,591 words, ~2,812 tokens.

Download SKILL.mdSave it as .claude/skills/redlamp-manual/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
redlamp-manual
description
The Redlamp User Manual (docs/manual), a dense, book-style PDF for photographers, typeset from Markdown and a print style sheet by Chrome, with its ranges, defaults and shortcuts generated from the app's code. Knows the manual's sources, its Markdown additions, figures and generated tables, the build and its checks, its page design, and how a part is researched and written. Use when writing, editing, building or reviewing the user manual, adding a part, section, figure or table to it, changing its look, or bringing it up to date with the app.

The Redlamp User Manual

The manual explains Redlamp to photographers, task by task: what each panel and tool is for, how to use it, and every control with its range, default and shortcut. It leaves out the engine's internals; that was the owner's choice. Its look and density follow a technical manual the owner liked, the Pi Durable Technical Manual, adapted to Redlamp's brand (design.md). Its rule is that manual's too: nothing is written from memory. Every label, range, default, shortcut and message comes from the code, each section ends with the files it was written from, and the slider and shortcut tables are generated when the manual is built.

Where

PathWhat
docs/manual/book.tomlEvery part and section, written or not. A section with a file is written; the rest show in the contents as the plan. Front matter is under [[front]]
docs/manual/content/<part>/<section>.mdA section: TOML front matter between +++ lines (deck, sources), then Markdown
docs/manual/facts/<part>.mdThe fact sheet a part was written from, a source for every fact
docs/manual/figures/<name>.htmlA figure: title:, tag: and caption: lines, ---, then its HTML or SVG
docs/manual/cover.htmlThe cover; {{repo}}, {{parts}}, {{commit}} and the like are filled in
docs/manual/style/manual.cssThe print style sheet: pages, type, figures and the cover
scripts/manual/The build: build.py (prints and pages), layout.py (the HTML), markup.py (the Markdown), tables.py and catalog.py (generated tables), fonts.py, and grid.py (screenshot coordinates)
build/manual/Output, gitignored: redlamp-manual.pdf, its HTML, pages/ previews, the fonts and the virtualenv

The workstream canvas is ~/.cursor/projects/Users-pedrogomes-src-darkroom/canvases/ws-user-manual.canvas.tsx. Read the owner's marks on its Needs you first, since the open design decisions are there, and keep it current as .cursor/skills/workstream-canvas/SKILL.md says.

Build

The first time, from the checkout's root:

bash
python3 -m venv build/manual/venv
build/manual/venv/bin/pip install markdown-it-py mdit-py-plugins playwright pymupdf

Then, with PNGs of the pages you're working on and contact sheets of the whole book:

bash
build/manual/venv/bin/python scripts/manual/build.py --pages 7-10 --sheets
  • A build takes about ten seconds. It downloads the fonts once and checks their hashes, then prints with the installed Chrome through Playwright, which downloads no browser. Chrome can't number pages in the contents or in cross-references, so the build prints again until no page moves: each measuring print ends with a page of links to every id, and the PDF's link targets give each one's page. The last print, without that page and with bookmarks, is build/manual/redlamp-manual.pdf.
  • --pages writes PNGs at 110 dpi and --sheets contact sheets of 15 pages each, to build/manual/pages/. --html writes only the HTML, to open in Chrome.
  • A warning about a font that isn't the manual's own means Chrome fell back to a system font for a character Inter doesn't have (⋯ did): use another character. The PDF embeds Inter, Inter Display and JetBrains Mono and nothing else.
  • The build stops on a cross-reference to an id nothing defines, a heading id used twice, or a generated table whose source in the app has changed shape.

Writing a section

  1. Facts first. Gather the part's facts from the code into docs/manual/facts/<part>.md, with a path and line for every fact, inferences marked, and every disagreement between the README and the code. A subagent does this well, given the prompt in fact-sheet.md. Check anything surprising in the code yourself before you write it.
  2. Plan it in book.toml. Give the section a file. Numbers follow the order: the part's number, then 3.1, 3.2 and so on. A heading's id is the section's id, a dot and the heading's slug, as in masking.ai.downloading-a-model.
  3. Write it by the rules below. Its front matter has deck, one or two sentences that summarise it in italics under the title, and sources, each file it was written from with what was used.
  4. Build, and look at every page it touches as PNGs, with the checklist.
  5. Commit on your own branch, naming the part (User manual: Part 2, white balance and tone), and update the canvas.
Rules for the text
  • For photographers, and task-focused: what a tool is for, how to use it (numbered steps for a task), then each of its controls. No engine internals: kernels, caches, process versions and how a model works stay out; downloads, their sizes and licences go in.
  • Every claim traces to the fact sheet or the code. Where the README and the code disagree, follow the code and add the disagreement to the canvas's Needs you. Never repeat a string the code has wrong; say what happens instead.
  • Name labels exactly as the app shows them (click Create New Mask, choose Duplicate and Invert). Write menus with › (Settings › Models), and right-click for a context menu. Give values as the slider's field shows them (+0.30, 100), ranges from the slider's left end to its right, and negative numbers with − (U+2212).
  • Write in the brand's voice (docs/brand/README.md): calm, plain and precise, without superlatives or exclamation marks. Spell in British English (colour, licence, grey), but keep the app's names as they are (Color Range, Color Overlay).
  • Say where Redlamp differs from Lightroom Classic in a ::: lightroom callout, and only as far as docs/lightroom-comparison.md supports. Claim nothing about Lightroom from memory.
  • Never put a cross-reference inside parentheses, since its page number brings its own: write "see " or "described under ".
Markdown additions
WriteGet
[[⇧W]], [[Esc]]Keycaps, one per key with the modifiers first, as the app's Keyboard Shortcuts sheet draws them. The [ and ] keys need <kbd>[</kbd>
::: note, ::: tip, ::: lightroom, ::: caution, ::: not-yet, closed by :::A callout. Words after the kind replace its label: ::: caution Pre-alpha
[](#id)The id's label (3.2, Fig. 3.1, Part 3, or a heading's words) with its page. [words](#id) keeps the words. A section that isn't written yet shows as its number, without a link
{{figure: name}}figures/name.html, numbered in order within its part
{{table: sliders id id …}}Each slider's range, default and arrow-key step from ParameterCatalog; the ids are ParameterID cases, such as localExposure
{{table: shortcuts id … @Category}}Each action's keys and title from ShortcutAction. @Masking adds a whole ShortcutCategory; write a name with spaces with underscores, as in @Rating_&_Flags
{{commit}}, {{date}}The last commit to change packages/ or apps/: the commit the manual describes, also on the cover
A term, then : what it does on the next lineRows of terms and their descriptions
A numbered listSteps, numbered in circles
Show full SKILL.md (569 more words)Show less

Figures

  • A figure file starts with title:, tag: (one word at the top right, such as Panel or Model), caption: (inline Markdown, its first sentence in bold) and, if needed, class:, then --- and the body. In the body, {{repo}} is the path from the HTML to the repository, for images. Blank lines in the body are removed, because a blank line would end the HTML block.
  • Diagrams are inline SVG drawn with the classes in manual.css (op-frame, op-fill, op-a, op-b, g-line, g-dash, g-handle, g-pin, g-text, g-note, g-mono and the rest), so they take the part's accent. Ids inside an SVG, for a <mask>, <clipPath> or gradient, must be unique in the whole manual: begin them with the figure's name.
  • Screenshots come from the app, never mock-ups: from docs/images, captured by scripts/capture-hero.sh, capture-promo.sh and capture-screenshots.sh with scripted edits, or a capture of your own made the same way. Show part of one with a .crop, its --crop-* and --image-* sizes given in the image's pixels. Number what matters with marks in the gutters beside it (.shot.gutters, .mark.l or .mark.r, top in percent), level with what they point at, and a .key list beside the image.
  • Find where marks go with build/manual/venv/bin/python scripts/manual/grid.py <image> <x0> <y0> <x1> <y1>, which draws the image's own pixel coordinates over the crop.
  • A list in a figure that isn't steps needs class="key", or it gets circled step numbers of its own.

Page design

Keep to design.md: what the reference's look is made of, and how the manual adapts each part to the brand. In short: A4 pages; Inter for text, Inter Display for headings and JetBrains Mono for labels and code, and no other font; ink on the brand's paper; dark part openers in wall, lit by the website's lamp glow, which with the logo's disc and the screenshots is the only red in the manual; the logo files on the cover, never the wordmark retyped; and each part's accent taken from one Color Mixer band's hue. A change to the look is the owner's to make: show them pages before and after.

Checking

At the pages you changed, as PNGs, and on the contact sheets:

  • The build printed no warning, and the page count is what you expect.
  • Every cross-reference has its page, and none sits inside parentheses.
  • In figures, marks are level with what they point at and cover nothing, labels are clear of lines, and nothing runs past a frame.
  • No heading is alone at the foot of a page, and no table is apart from its heading.
  • Every value in the text matches the generated tables and the fact sheet.
  • The contents and the part's opener list the section with its page.

Keeping it current

The manual describes the commit on its cover. Generated tables follow the code at every build; the text doesn't. When a feature changes, find the sections whose sources name its files, check them against the code, and correct the fact sheet with them. Other sessions change the app all the time, so check a part's fact sheet against the code before you rely on it.

Alongside other sessions

The manual has paths of its own (docs/manual/, scripts/manual/ and this skill) and changes nothing else. Work on your own branch in a worktree, as AGENTS.md says. During an agent wave web/ is off limits, so a web version of the manual waits until the owner opens it.

© pdcgomes, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in .cursor/skills/redlamp-manual of pdcgomes/redlamp.

  • SKILL.md
  • design.md
  • fact-sheet.md

Open the folder on GitHubat commit 9587460

Compare with similar skills

Redlamp Manual 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.

Redlamp Manual compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Redlamp Manual this skillpdcgomes/redlamp231—~2.8kAutomated safety check: PassMPL-2.0
Insight Error Pagevercel/next.js143k—~5.5kAutomated safety check: PassMIT
Markdown Paged GuideBigStrongSun/ccswitchmulti121—~589Automated safety check: PassMIT
ISO 24495 Text AuditGaZmagik/iso-24495190—~817Automated safety check: PassMIT
Mintlify Claude Docslilinji/ai-infra-odyssey130—~8.2kAutomated safety check: PassNone
Markdown Article FormatterJimLiu/baoyu-skills27k6 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Insight Error Page

    vercel/next.js

    Official

    Write or audit an insight-kind error page for the Next.js dev overlay.

    143k GitHub stars~5.5k tokensUpdated today
    Writing & ContentAuto-check passed

  • Markdown Paged Guide

    BigStrongSun/ccswitchmulti

    Render Markdown manuals into polished per-page PNG images and PDF deliverables.

    121 GitHub stars~589 tokensUpdated 6 days ago
    Documents & OfficeAuto-check passed

  • ISO 24495 Text Audit

    GaZmagik/iso-24495

    Audits a Markdown or text file or folder you choose for plain-language problems such as legalese, wordy phrases and long sentences, reporting each finding with file and line.

    190 GitHub stars~817 tokensUpdated yesterday
    Writing & ContentAuto-check passed

  • Mintlify Claude Docs

    lilinji/ai-infra-odyssey

    Build, write, review, migrate, and maintain Mintlify documentation in a restrained Claude Docs-inspired style.

    130 GitHub stars~8.2k tokensUpdated 12 days ago
    Writing & ContentAuto-check passed

  • Markdown Article Formatter

    JimLiu/baoyu-skills

    Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.

    27k GitHub starsUsed in 6 repos~3.5k tokens
    Documents & OfficeAuto-check passed

  • Bookforge Korean Ebook PDF Maker

    gongnyang/bookforge

    Produces book-style Korean ebook PDFs from a topic or finished manuscript, with six design styles, real book parts and quality-check gates before output.

    316 GitHub starsUsed in 1 repo~1.7k tokens
    Documents & OfficeAuto-check passed

More from pdcgomes/redlamp

All 11 skills in this repo

  • Redlamp Bench

    pdcgomes/redlamp

    Redlamp Bench, the way an agent asks the owner to do a step in another app and gets the results back without anyone moving files.

    231 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Redlamp Promo Studio

    pdcgomes/redlamp

    The promo studio, which makes Redlamp's short promotional videos for social feeds the way a small creative agency does - a brief, hooks and copy, a script on a music grid, visuals from the promo…

    231 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Redlamp Site

    pdcgomes/redlamp

    Map of redlamp.app, the Next.js website in web/: its stack and commands, its pages, the home page's sections with their anchors, components and content sources, the brand's Tailwind tokens and…

    231 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Redlamp Blog

    pdcgomes/redlamp

    The blog room, where every redlamp.app blog post is tracked from idea to announcement in a canvas the owner marks as they post.

    231 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Redlamp Press

    pdcgomes/redlamp

    The press room, where every outlet Redlamp is pitched to (newsletters, Mac and photography sites, developer and open-source communities, lists and directories) is tracked from finding it to its…

    231 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Redlamp Release

    pdcgomes/redlamp

    The release room, where every Redlamp release is prepared, checked, approved and shipped.

    231 GitHub stars~3.8k tokensUpdated today
    Auto-check passed

Categories

Questions about Redlamp Manual

What does Redlamp Manual do?

The Redlamp User Manual (docs/manual), a dense, book-style PDF for photographers, typeset from Markdown and a print style sheet by Chrome, with its ranges, defaults and shortcuts generated from the…. Redlamp Manual is an agent skill from pdcgomes/redlamp. The Redlamp User Manual (docs/manual), a dense, book-style PDF for photographers, typeset from Markdown and a print style sheet by Chrome, with its ranges, defaults and shortcuts generated from the app's code.

When should I use Redlamp Manual?

Redlamp Manual fits situations like: reviewing the user manual; changing its look; bringing it up to date with the app.

How do I install Redlamp Manual in Claude Code?

Run `npx skills add pdcgomes/redlamp --skill redlamp-manual -a claude-code`. Or copy the skill folder (.cursor/skills/redlamp-manual in pdcgomes/redlamp) into .claude/skills/redlamp-manual in your project. Claude Code loads it when a task matches its description.

How do I install Redlamp Manual in Codex?

Run `npx skills add pdcgomes/redlamp --skill redlamp-manual -a codex`. Or copy the skill folder (.cursor/skills/redlamp-manual in pdcgomes/redlamp) into .agents/skills/redlamp-manual in your project. Codex loads it when a task matches its description.

Can I use Redlamp Manual 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 pdcgomes/redlamp --skill redlamp-manual -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/redlamp-manual, .gemini/skills/redlamp-manual, .github/skills/redlamp-manual and .opencode/skills/redlamp-manual in your project.

What does Redlamp Manual need to run?

Going by SKILL.md and its folder, Redlamp Manual needs the command-line tools its instructions call (python, python3 and pip). Our summary lists: Python 3.

Does Redlamp Manual access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Redlamp Manual 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 Redlamp Manual use?

Redlamp Manual is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Redlamp Manual use?

About 2.8k tokens (SKILL.md is roughly 11k 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 Redlamp Manual?

Skills that share tags, products or a category with Redlamp Manual: Insight Error Page (vercel/next.js, 143k stars), Markdown Paged Guide (BigStrongSun/ccswitchmulti, 121 stars), ISO 24495 Text Audit (GaZmagik/iso-24495, 190 stars) and Mintlify Claude Docs (lilinji/ai-infra-odyssey, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Redlamp Manual?

pdcgomes (a GitHub user) maintains it in pdcgomes/redlamp, which has 231 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 11, 2026.

Source: pdcgomes/redlamp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.