A skill your agent uses when improving a public README, repository homepage, docs landing page, or developer-facing first impression.

MITAuto-check passedFrontend & Design

Install Public Readme Polisher

skills CLI
$ npx skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill public-readme-polisher -a claude-code

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

GitHub CLI
$ gh skill install 100yenadmin/fable-token-saving-skills-orchestrator public-readme-polisher --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/100yenadmin/fable-token-saving-skills-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/public-readme-polisher .claude/skills/public-readme-polisher && 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
public-readme-polisher
GitHub stars
100
Token cost
~784 tokens
SKILL.md length
422 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when improving a public README, repository homepage, docs landing page, or developer-facing first impression.

  • Works in 5 steps: Audit repo truth: purpose, install path,… → Define the public promise in one… → Improve the first viewport: title,… → …
  • Improving a public README
  • SKILL.md covers Use When, Process, Visual Asset Rules and Claim Safety, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Public Readme Polisher is an agent skill from 100yenadmin/fable-token-saving-skills-orchestrator. Use when improving a public README, repository homepage, docs landing page, or developer-facing first impression.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Technical documentation and Landing pages. The repository describes itself as: 🧚 Fable-first Claude orchestration kit for token-saving lane routing, dense turns, and cache-preserving wait discipline. The licence is MIT.

When your agent uses it

  • Improving a public README
  • Repository homepage
  • Docs landing page
  • Developer-facing first impression

Example prompts

  • “/public-readme-polisher”

Workflow steps

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

  1. Audit repo truth: purpose, install path, tests, license, security, CI, docs,
  2. Define the public promise in one paragraph: who it helps, what it gives
  3. Improve the first viewport: title, optional hero, badges, concise opening,
  4. Add scanning structure: quick start, workflow diagram when useful, proof or
  5. Validate links, images, alt text, docs scan, tests, and the scorecard below.

What it can do on your machine

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

Public Readme Polisher loads about 784 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 422 words of instructions outside code blocks.

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

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 100yenadmin/fable-token-saving-skills-orchestrator at commit cf1d9a3, republished under its MIT licence (© 100yenadmin). 422 words, ~784 tokens.

Download SKILL.mdSave it as .claude/skills/public-readme-polisher/SKILL.md (or your agent's skills folder).
name
public-readme-polisher
description
Use when improving a public README, repository homepage, docs landing page, or developer-facing first impression.

Public README Polisher

Polish the README as the repo's public front door: credible, scannable, actionable, and claim-safe.

Use When

  • a README feels plain
  • a repo needs a public first impression
  • a docs landing page needs clearer value, install path, or proof
  • a visual asset could make the repo easier to understand

Process

  1. Audit repo truth: purpose, install path, tests, license, security, CI, docs, examples, and public claim boundaries.
  2. Define the public promise in one paragraph: who it helps, what it gives them, and what it does not guarantee.
  3. Improve the first viewport: title, optional hero, badges, concise opening, quick action, and a scannable "what you get" table.
  4. Add scanning structure: quick start, workflow diagram when useful, proof or sources near the claim, and links to deeper docs.
  5. Validate links, images, alt text, docs scan, tests, and the scorecard below.

Visual Asset Rules

  • Use one purposeful hero only when it clarifies the repo.
  • For generated images: no embedded text, no logos, no watermarks.
  • Inspect the image before committing; reject generated image with readable fake text, broken UI, mascot drift, or misleading claims.
  • Save README assets under assets/readme.
  • Add alt text that explains the image function.

Claim Safety

  • Cite official sources for factual pricing, cache, legal, API, or security claims.
  • Say "patterns that worked for us" for experience-based recommendations.
  • Avoid guaranteed savings, official endorsement, universal safety claims, or "works for every workflow" language.
  • Keep related tools optional unless the repo truly depends on them.
Show full SKILL.md (175 more words)Show less

Scorecard

Score each category 0-2. Pass at 13/16 or higher.

Category2 means
First-viewport signalrepo purpose, visual tone, badges, and install path are clear without scrolling
Audience/value clarityreader knows who it is for and what problem it solves
Scannabilitytables, bullets, headings, and diagrams make scanning easy
Actionabilityquick start and next links are concrete and current
Trust/proofsources, CI, license, tests, and safety boundaries support the claims
Visual polishassets feel intentional, domain-fit, and not generic stock decoration
Accessibility/asset hygienealt text, local paths, file size, and image rendering are sane
Claim safetyclaims are bounded, sourced where needed, and public-safe

Automatic blockers: private paths, secrets, broken local links, missing install path, false or guaranteed claims, generated image with readable fake text, missing alt text, failing docs scan.

Common Mistakes

  • Making a marketing page that hides the actual install/use path.
  • Adding a pretty image that does not explain the repo.
  • Moving official citations away from the claims they support.
  • Replacing precise safety boundaries with vague hype.
  • Claiming completion without running the scorecard.

© 100yenadmin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/public-readme-polisher of 100yenadmin/fable-token-saving-skills-orchestrator.

Open the folder on GitHubat commit cf1d9a3

Compare with similar skills

Public Readme Polisher 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.

Public Readme Polisher compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Public Readme Polisher this skill100yenadmin/fable-token-saving-skills-orchestrator100—~784Automated safety check: PassMIT
Aif Docsunxed/f4243—~5.7kAutomated safety check: PassBSD-3-Clause
Docskmworks/kmreader113—~551Automated safety check: PassMIT
Docs UpdateJayFarei/opentraces100—~4.6kAutomated safety check: PassCustom licence
Refactoring UIs0xDk/refactoring-ui-skill595—~3.5kAutomated safety check: PassMIT
Lofisu Personazclllyybb/lofisu-identity-engine454—~2.8kAutomated safety check: PassUnlicense

Similar skills

  • Aif Docs

    unxed/f4

    Generate and maintain project documentation. An agent skill from unxed/f4.

    243 GitHub stars~5.7k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Docs

    kmworks/kmreader

    Regenerate README.md, APPSTOREDESCRIPTION.txt, and the KMReader landing page (src/pages/reader/index.tsx in the kmworks/website repo) based on current important product features in the codebase.

    113 GitHub stars~551 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Docs Update

    JayFarei/opentraces

    Synchronize all documentation surfaces after code changes. An agent skill from JayFarei/opentraces.

    100 GitHub stars~4.6k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Refactoring UI

    s0xDk/refactoring-ui-skill

    Design and improve user interfaces using the concrete rules from Refactoring UI (Wathan & Schoger) — constrained spacing/type/color/shadow scales, visual hierarchy through weight and color rather…

    595 GitHub stars~3.5k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Lofisu Persona

    zclllyybb/lofisu-identity-engine

    LofiSu的行为人格Skill。基于GitHub公开数据(282次commit/150次README迭代/50+fork/100+contribution) 的Codex深度挖掘分析报告+小红书卖课行为报告的系统蒸馏, 提炼6个核心心智模型、8条决策启发式和完整的表达DNA。

    454 GitHub stars~2.8k tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Auto Improve

    crimeacs/auto-improve

    GAN-style iterative improvement loop for any text artifact. An agent skill from crimeacs/auto-improve.

    135 GitHub stars~651 tokensUpdated 2 mo ago
    EducationAuto-check passed

More from 100yenadmin/fable-token-saving-skills-orchestrator

  • Codex Dispatch

    100yenadmin/fable-token-saving-skills-orchestrator

    A skill your agent uses when routing well-specified implementation work from Fable to Codex or another side worker.

    100 GitHub stars~658 tokensUpdated 3 mo ago
    Auto-check passed
  • Public Repo Operationalizer

    100yenadmin/fable-token-saving-skills-orchestrator

    A skill your agent uses when preparing a repository, project kit, plugin, skillpack, or developer tool for public release or maintainer-ready public operations.

    100 GitHub stars~829 tokensUpdated 3 mo ago
    Auto-check passed
  • Run Economics

    100yenadmin/fable-token-saving-skills-orchestrator

    A skill your agent uses when choosing between cheap probes, worker runs, expensive ruler runs, or long keepalive waits.

    100 GitHub stars~226 tokensUpdated 3 mo ago
    Auto-check passed
  • Fable Orchestrator Router

    100yenadmin/fable-token-saving-skills-orchestrator

    Use before delegating work from a Fable or premium-model orchestration session.

    100 GitHub stars~316 tokensUpdated 3 mo ago
    Auto-check passed

Questions about Public Readme Polisher

What does Public Readme Polisher do?

A skill your agent uses when improving a public README, repository homepage, docs landing page, or developer-facing first impression. Public Readme Polisher is an agent skill from 100yenadmin/fable-token-saving-skills-orchestrator. Use when improving a public README, repository homepage, docs landing page, or developer-facing first impression.

When should I use Public Readme Polisher?

Public Readme Polisher fits situations like: improving a public README; repository homepage; docs landing page; developer-facing first impression.

How do I install Public Readme Polisher in Claude Code?

Run `npx skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill public-readme-polisher -a claude-code`. Or copy the skill folder (skills/public-readme-polisher in 100yenadmin/fable-token-saving-skills-orchestrator) into .claude/skills/public-readme-polisher in your project. Claude Code loads it when a task matches its description.

How do I install Public Readme Polisher in Codex?

Run `npx skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill public-readme-polisher -a codex`. Or copy the skill folder (skills/public-readme-polisher in 100yenadmin/fable-token-saving-skills-orchestrator) into .agents/skills/public-readme-polisher in your project. Codex loads it when a task matches its description.

Can I use Public Readme Polisher 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 100yenadmin/fable-token-saving-skills-orchestrator --skill public-readme-polisher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/public-readme-polisher, .gemini/skills/public-readme-polisher, .github/skills/public-readme-polisher and .opencode/skills/public-readme-polisher in your project.

What does Public Readme Polisher need to run?

SKILL.md names no scripts, command-line tools or credentials: Public Readme Polisher is instructions for the agent only.

Does Public Readme Polisher 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 Public Readme Polisher 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 Public Readme Polisher use?

Public Readme Polisher is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Public Readme Polisher use?

About 784 tokens (SKILL.md is roughly 3.1k 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 Public Readme Polisher?

Skills that share tags, products or a category with Public Readme Polisher: Aif Docs (unxed/f4, 243 stars), Docs (kmworks/kmreader, 113 stars), Docs Update (JayFarei/opentraces, 100 stars) and Refactoring UI (s0xDk/refactoring-ui-skill, 595 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Public Readme Polisher?

100yenadmin (a GitHub user) maintains it in 100yenadmin/fable-token-saving-skills-orchestrator, which has 100 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on July 4, 2026.

Source: 100yenadmin/fable-token-saving-skills-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.