Chinese Indie Dev
1c7/chinese-independent-developer
处理 1c7/chinese-independent-developer 仓库的项目提交. An agent skill from 1c7/chinese-independent-developer.
Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.
Install Build In Public Launcher
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills build-in-public-launcher --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/build-in-public-launcher .claude/skills/build-in-public-launcher && rm -rf skills-srcUse ~/.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/
Install the "build-in-public-launcher" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/build-in-public-launcher into .claude/skills/build-in-public-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-in-public-launcher", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/build-in-public-launcherType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills build-in-public-launcher --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/build-in-public-launcher .agents/skills/build-in-public-launcher && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "build-in-public-launcher" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/build-in-public-launcher into .agents/skills/build-in-public-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-in-public-launcher", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills build-in-public-launcher --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/build-in-public-launcher .cursor/skills/build-in-public-launcher && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "build-in-public-launcher" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/build-in-public-launcher into .cursor/skills/build-in-public-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-in-public-launcher", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FAIRY123456789/human-edge-agent-skills.git --path skills/build-in-public-launcher--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills build-in-public-launcher --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/build-in-public-launcher .gemini/skills/build-in-public-launcher && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "build-in-public-launcher" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/build-in-public-launcher into .gemini/skills/build-in-public-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-in-public-launcher", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FAIRY123456789/human-edge-agent-skills build-in-public-launcherInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/build-in-public-launcher .github/skills/build-in-public-launcher && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "build-in-public-launcher" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/build-in-public-launcher into .github/skills/build-in-public-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-in-public-launcher", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills build-in-public-launcher --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/build-in-public-launcher .opencode/skills/build-in-public-launcher && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "build-in-public-launcher" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/build-in-public-launcher into .opencode/skills/build-in-public-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-in-public-launcher", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
build-in-public-launcher- GitHub stars
- 103
- Token cost
- ~708 tokens
- SKILL.md length
- 312 words
- Files
- 3 (incl. references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.
- Works in 10 steps: Define the exact user and painful moment… → Audit whether the artifact is actually… → Write a one-line value proposition that… → …
- The work exists but nobody outside the creator has tried it
- SKILL.md covers Purpose, Instructions, Default launch horizon and Output, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Build In Public Launcher is an agent skill from FAIRY123456789/human-edge-agent-skills. Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback. Use when the work exists but nobody outside the creator has tried it, the README is weak, the launch has no demo or proof metric, or the user wants a GitHub-first build-in-public plan without fake traction or vanity metrics.
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/launch-pack.md`).
It sits in Development, covering Technical documentation. It works with GitHub. The repository describes itself as: 18 portable Agent Skills for voice-native AI, human judgment, microbets, social tact, writing, life systems, and safe deployment. The licence is MIT.
When your agent uses it
- The work exists but nobody outside the creator has tried it
- The README is weak
- The launch has no demo
- The user wants a GitHub-first build-in-public plan without fake traction
Example prompts
- “/build-in-public-launcher”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Define the exact user and painful moment the artifact addresses.
- Audit whether the artifact is actually ready for a stranger: installation, first-run path, example input, example output, license, privacy…
- Write a one-line value proposition that names the job, not the technology stack.
- Build a launch pack using references/launch-pack.md.
- Create one comparison or task-completion demo. Do not cherry-pick an impossible-to-reproduce showcase.
- Choose one primary proof metric and one secondary distribution metric.
- Recruit the first testers from existing communities, peers, contributors, or target-user groups. Prefer 10 relevant people over 1,000…
- Ask testers to perform a task before explaining the solution. Capture confusion and failure.
- Publish a changelog entry after each evidence-driven revision.
- Promote measured adoption only after it exists. Never invent stars, users, installs, revenue, benchmarks, or testimonials.
What it can do on your machine
Read from SKILL.md and the folder at commit 31a0a16. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Build In Public Launcher loads about 708 tokens when it runs, and up to ~905 if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 312 words of instructions outside code blocks.
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 FAIRY123456789/human-edge-agent-skills at commit 31a0a16, republished under its MIT licence (© FAIRY123456789). 312 words, ~708 tokens.
Download SKILL.mdSave it as
.claude/skills/build-in-public-launcher/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- build-in-public-launcher
- description
- Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback. Use when the work exists but nobody outside the creator has tried it, the README is weak, the launch has no demo or proof metric, or the user wants a GitHub-first build-in-public plan without fake traction or vanity metrics.
- license
- MIT
- metadata.author
- Joy T <101039451+FAIRY123456789@users.noreply.github.com>
- metadata.tags
- product-launch, open-source, validation
Build in Public Launcher
Purpose
Launch for evidence, not applause. This Skill turns a finished artifact into a bounded release and feedback loop without inventing adoption.
Instructions
- Define the exact user and painful moment the artifact addresses.
- Audit whether the artifact is actually ready for a stranger: installation, first-run path, example input, example output, license, privacy and security notes, and failure handling.
- Write a one-line value proposition that names the job, not the technology stack.
- Build a launch pack using
references/launch-pack.md. - Create one comparison or task-completion demo. Do not cherry-pick an impossible-to-reproduce showcase.
- Choose one primary proof metric and one secondary distribution metric.
- Recruit the first testers from existing communities, peers, contributors, or target-user groups. Prefer 10 relevant people over 1,000 generic impressions.
- Ask testers to perform a task before explaining the solution. Capture confusion and failure.
- Publish a changelog entry after each evidence-driven revision.
- Promote measured adoption only after it exists. Never invent stars, users, installs, revenue, benchmarks, or testimonials.
Default launch horizon
Use a 7-day launch loop:
- Day 1: packaging and smoke test
- Day 2: private testers
- Day 3–4: fix onboarding and failure cases
- Day 5: public release
- Day 6–7: collect issues, repeat use, and outcome evidence
Output
Return a release-ready checklist, README hero copy, demo plan, tester plan, proof metrics, and 7-day launch schedule.
Examples
- Input: a working repository with no external users and a confusing README.
- Output: a reproducible demo, a first-tester plan, one utility metric, and explicit stop or iterate criteria.
Limitations
Do not claim market demand, compatibility, or traction that has not been observed. Publishing, messaging testers, and changing external accounts require the user's explicit authorization.
Troubleshooting
If no credible metric exists, choose successful task completion or tester confusion as the first measurement. If strangers cannot install the artifact, return to packaging before writing launch copy.
© FAIRY123456789, MIT. 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 (references) in skills/build-in-public-launcher of FAIRY123456789/human-edge-agent-skills.
- SKILL.md
- README.md
- references/launch-pack.md
Open the folder on GitHubat commit 31a0a16
Compare with similar skills
Build In Public Launcher 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Build In Public Launcher this skillFAIRY123456789/human-edge-agent-skills | 103 | — | ~708 | Automated safety check: Pass | MIT | |
| Chinese Indie Dev1c7/chinese-independent-developer | 62k | — | ~8.7k | Automated safety check: Pass | None | |
| Update .NET OS Packagesdotnet/core | 22k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Beautify GitHub Readmeoil-oil/beautify-github-readme | 1.8k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Update .NET Supported OS Matrixdotnet/core | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Debate ReviewamElnagdy/review-skills | 132 | 2 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Update .NET OS Packages
dotnet/core
Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.
Beautify GitHub Readme
oil-oil/beautify-github-readme
Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets.
- Official
Update .NET Supported OS Matrix
dotnet/core
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
Debate Review
amElnagdy/review-skills
Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.
Library Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
More from FAIRY123456789/human-edge-agent-skills
All 18 skills in this repoAliyun Fullstack Deploy
FAIRY123456789/human-edge-agent-skills
Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.
Skill From Scars
FAIRY123456789/human-edge-agent-skills
Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.
Voice Dump To Todo
FAIRY123456789/human-edge-agent-skills
Convert a long, messy, repetitive, speech-recognition-heavy task dump into a precise executable to-do list.
Deployment Proof
FAIRY123456789/human-edge-agent-skills
Convert deployment logs, validation reports, Git history, and comparison notes into a redacted GitHub case study, portfolio entry, interview story, and evidence-backed resume bullets.
Vibe To Spec
FAIRY123456789/human-edge-agent-skills
Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…
Small Server Fit
FAIRY123456789/human-edge-agent-skills
Assess whether a web application and its build and runtime plan fit a low-cost Linux VPS or Alibaba Cloud ECS before purchase, implementation, or deployment.
Related
Works with
Categories
Questions about Build In Public Launcher
What does Build In Public Launcher do?
Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback. Build In Public Launcher is an agent skill from FAIRY123456789/human-edge-agent-skills. Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.
When should I use Build In Public Launcher?
Build In Public Launcher fits situations like: the work exists but nobody outside the creator has tried it; the README is weak; the launch has no demo; the user wants a GitHub-first build-in-public plan without fake traction.
How do I install Build In Public Launcher in Claude Code?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a claude-code`. Or copy the skill folder (skills/build-in-public-launcher in FAIRY123456789/human-edge-agent-skills) into .claude/skills/build-in-public-launcher in your project. Claude Code loads it when a task matches its description.
How do I install Build In Public Launcher in Codex?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a codex`. Or copy the skill folder (skills/build-in-public-launcher in FAIRY123456789/human-edge-agent-skills) into .agents/skills/build-in-public-launcher in your project. Codex loads it when a task matches its description.
Can I use Build In Public Launcher 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 FAIRY123456789/human-edge-agent-skills --skill build-in-public-launcher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-in-public-launcher, .gemini/skills/build-in-public-launcher, .github/skills/build-in-public-launcher and .opencode/skills/build-in-public-launcher in your project.
What does Build In Public Launcher need to run?
SKILL.md names no scripts, command-line tools or credentials: Build In Public Launcher is instructions for the agent only.
Does Build In Public Launcher access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Build In Public Launcher 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 Build In Public Launcher use?
Build In Public Launcher is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Build In Public Launcher use?
About 708 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 197 tokens, read only when the agent opens those files.
What are the alternatives to Build In Public Launcher?
Skills that share tags, products or a category with Build In Public Launcher: Chinese Indie Dev (1c7/chinese-independent-developer, 62k stars), Update .NET OS Packages (dotnet/core, 22k stars), Beautify GitHub Readme (oil-oil/beautify-github-readme, 1.8k stars) and Update .NET Supported OS Matrix (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Build In Public Launcher?
FAIRY123456789 (a GitHub user) maintains it in FAIRY123456789/human-edge-agent-skills, which has 103 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.
Source: FAIRY123456789/human-edge-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.