Agent skill

Redlamp Supporters

by pdcgomes in pdcgomes/redlamp

The supporters room, where Redlamp's funding is run in a canvas the owner approves and posts from.

MPL-2.0Auto-check passed

Install Redlamp Supporters

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

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

GitHub CLI
$ gh skill install pdcgomes/redlamp redlamp-supporters --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-supporters .claude/skills/redlamp-supporters && 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-supporters
GitHub stars
222
Token cost
~1.7k tokens
SKILL.md length
976 words
Files
2
Skills in repo
11
Repo updated
First seen
Licence
MPL-2.0

At a glance

The supporters room, where Redlamp's funding is run in a canvas the owner approves and posts from.

  • Works in 3 steps: Read the owner's marks first. Fold the… → Check what you report. Members and money… → Bring the room up to date in the same…
  • Working on Patreon
  • SKILL.md covers The promise, Where, Every time: know where things… and The pages, plus 5 more sections
  • Calls git and gh

What it does

Redlamp Supporters is an agent skill from pdcgomes/redlamp. The supporters room, where Redlamp's funding is run in a canvas the owner approves and posts from. It holds the Patreon page and redlamp.app/support, the tiers, what Redlamp costs and the funding ladder those figures make, the members' monthly letter, the quarterly ranking of what's built next, the supporters list, and the quarterly report of what came in and where it went. Use when working on Patreon, Ko-fi, GitHub Sponsors, memberships, donations or supporters; drafting the page, a letter, a ranking or a…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It works with GitHub. 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

  • Working on Patreon
  • GitHub Sponsors
  • Drafting the page
  • Updating the figures

Example prompts

  • “monthly letter, the quarterly ranking of what”
  • “/redlamp-supporters”

Workflow steps

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

  1. Read the owner's marks first. Fold the needsYou marks into room as .cursor/skills/workstream-canvas/SKILL.md describes, each post's mark…
  2. Check what you report. Members and money come from the platforms' exports or the owner's word, rows from the tracker, and commits from git…
  3. Bring the room up to date in the same turn: summary, stage, needsYou, plan, a log entry and updated. Say plainly what you didn't check.

What it can do on your machine

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

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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 Supporters loads about 1.7k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 976 words of instructions outside code blocks.

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

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 bc52683, republished under its MPL-2.0 licence (© pdcgomes). 976 words, ~1,709 tokens.

Download SKILL.mdSave it as .claude/skills/redlamp-supporters/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
redlamp-supporters
description
The supporters room, where Redlamp's funding is run in a canvas the owner approves and posts from. It holds the Patreon page and redlamp.app/support, the tiers, what Redlamp costs and the funding ladder those figures make, the members' monthly letter, the quarterly ranking of what's built next, the supporters list, and the quarterly report of what came in and where it went. Use when working on Patreon, Ko-fi, GitHub Sponsors, memberships, donations or supporters; drafting the page, a letter, a ranking or a report; updating the figures or the credits; or asking what support brings in and what it pays for.

The supporters room

Redlamp is free and open source, and support pays for the work: its running costs, its research and the owner's time. The supporters room is the canvas where that is run: the pages people join from, the tiers, the figures and the ladder they make, what's posted to members, and what came in and where it went. The owner approves the copy, enters the figures and posts everything himself; agents draft, gather the material and keep the room.

The promise

Every page, post and change keeps to it:

  • Nothing is held back for supporters: no feature, build or fix. Bugs are fixed by severity, never by tier.
  • Members set the order of work the owner has already accepted. They don't decide what goes on the roadmap, and Report a Bug and Send Feedback stay the same for everyone.
  • Money is reported in totals, and members are credited only as they ask to be.

Where

WhatWhere
The room~/.cursor/projects/Users-pedrogomes-src-darkroom/canvases/supporters-room.canvas.tsx, from template.tsx. Edit only its room object. A change to the rendering goes into the template and the room together.
The owner's marks and figuressupporters-room.canvas.data.json beside it: needsYou (Done, Skip, Ask the agent), posts (Posted, Scheduled, Skip) and figures (running costs, research budget, full-time income and Ko-fi so far, as he typed them). Only the canvas writes it.
The platformsPatreon for memberships, and Ko-fi (ko-fi.com/pdcgomes) for one-off tips. Once redlamp.app/support exists, every support link points at it, never straight at a platform: the app's SettingsView.supportURL, the README's badge and closing line, and web/lib/site.ts.
What never goes into the repositoryMembers' names (other than as they asked to be credited), emails, messages and what each pays, and the owner's figures until he publishes them. They stay in the room and its data file. The template holds the page drafts and nobody's details.

Read ~/.cursor/skills-cursor/canvas/SKILL.md once per session before the first edit of the room. Link the room in every reply that changes it: [Supporters room](/Users/pedrogomes/.cursor/projects/Users-pedrogomes-src-darkroom/canvases/supporters-room.canvas.tsx).

Every time: know where things stand

  1. Read the owner's marks first. Fold the needsYou marks into room as .cursor/skills/workstream-canvas/SKILL.md describes, each post's mark into its state, and the figures into room.figures, with the date in recorded. Never write the data file.
  2. Check what you report. Members and money come from the platforms' exports or the owner's word, rows from the tracker, and commits from git log, never from memory.
  3. Bring the room up to date in the same turn: summary, stage, needsYou, plan, a log entry and updated. Say plainly what you didn't check.

The pages

  • Patreon: the headline, About (with the ladder, built from the figures), each tier's description, the welcome note and the questions. redlamp.app/support: membership, Ko-fi, sample files on raw.pixls.us, Test Your Camera, and Report a Bug or Send Feedback. Both are drafted in room, and go nowhere until the owner approves them.
  • The ladder is cumulative: running costs, then the research budget, then a fifth, a half and all of the full-time income. The canvas turns each step into pledges a month at an average of $8 a member, after Patreon's fees at the rates its Money tab names (fee() in the template). Check those rates on Patreon's pricing page before the owner sets prices.
  • A change to a tier's price or perks changes the tiers, About, the questions and the support page together.
  • Write in the owner's voice, as .cursor/skills/redlamp-blog/SKILL.md describes (Writing in the owner's voice), and claim only what the README says.
Show full SKILL.md (397 more words)Show less

The monthly letter

Early each month, to every member, in about 400 words. Draft it from what the repository records for the month; the owner edits and posts it.

  • What shipped: the month's releases (gh release list) and their What's New, and the tracker rows that became Done (git log on docs/research/research-tracker.md).
  • What's next and why: the rows in progress, and the next ranked row.
  • What it cost: the month's costs and what came in, in totals.
  • Something learned: a research note or a measurement from the month (docs/research/notes/, the blog).

Add it to posts as a letter, with its audience and due date, and a Needs you item to post it.

The quarterly ranking

  1. Pick three to five rows that are Accepted and Not started, in the current phase and sized S or M, that the owner is happy to build next. He approves the shortlist (a Needs you item).
  2. Draft the poll for Insider and Studio members: each row in plain words, with its issue. Add it to posts as a ranking.
  3. Once the poll closes and the owner gives the result, the top row goes next. Add "supporters' pick" and the quarter to its Decision cell in the tracker (Accepted (2026-10-01): …; supporters' pick, 2027 Q1), sync the issues (.cursor/rules/tracker-issues.mdc), and draft the result for every member.

The quarterly report

At the end of each quarter, a post for everyone: members at the end of the quarter, what came in from Patreon and Ko-fi after fees, each cost, and what's left over and where it goes. Totals only. Add the quarter to money, and the post to posts as a report.

The supporters list

The welcome note asks each member how they'd like to be credited: by name, by a handle, or not at all. Only those who answer with a name or a handle are listed, in the app and on redlamp.app, with founding supporters (those who joined in the first month) marked. The list holds names only. It's built when the first member asks to be credited (the plan's credits step), and this skill then says where it lives.

Evolving the room

The owner shapes the room as needs come up. A new list, state or button goes into the template and this skill in the same change, and the room picks it up. Commit both on main: Supporters room: ….

© 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 1 other file in .cursor/skills/redlamp-supporters of pdcgomes/redlamp.

  • SKILL.md
  • template.tsx

Open the folder on GitHubat commit bc52683

Compare with similar skills

Redlamp Supporters 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 Supporters compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Redlamp Supporters this skillpdcgomes/redlamp222—~1.7kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Diagnosing Superpowers Sessionsobra/superpowers297k3 repos~1.7kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    297k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed
  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes

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.

    222 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Redlamp Manual

    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…

    222 GitHub stars~2.8k 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…

    222 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…

    222 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.

    222 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…

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

Works with

Questions about Redlamp Supporters

What does Redlamp Supporters do?

The supporters room, where Redlamp's funding is run in a canvas the owner approves and posts from. Redlamp Supporters is an agent skill from pdcgomes/redlamp. The supporters room, where Redlamp's funding is run in a canvas the owner approves and posts from.

When should I use Redlamp Supporters?

Redlamp Supporters fits situations like: working on Patreon; GitHub Sponsors; drafting the page; updating the figures.

How do I install Redlamp Supporters in Claude Code?

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

How do I install Redlamp Supporters in Codex?

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

Can I use Redlamp Supporters 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-supporters -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-supporters, .gemini/skills/redlamp-supporters, .github/skills/redlamp-supporters and .opencode/skills/redlamp-supporters in your project.

What does Redlamp Supporters need to run?

Going by SKILL.md and its folder, Redlamp Supporters needs the command-line tools its instructions call (git and gh).

Does Redlamp Supporters access the network?

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

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

Redlamp Supporters 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 Supporters use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Supporters?

Skills that share tags, products or a category with Redlamp Supporters: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Diagnosing Superpowers Sessions (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Redlamp Supporters?

pdcgomes (a GitHub user) maintains it in pdcgomes/redlamp, which has 222 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 10, 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.