Improves GitHub discoverability: README anatomy and badges, username profile README, topics, awesome-list submissions, FUNDING.yml, and traffic/star signals. Use for making a repo findable via README, topics, profile page, or awesome-list PRs. Not for Actions log debugging, PR merge mechanics, or application feature work.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Improves GitHub discoverability: README anatomy and badges, username profile README, topics, awesome-list submissions, FUNDING.yml, and traffic/star signals. Use for making a repo findable via README, topics, profile page, or awesome-list PRs. Not for Actions log debugging, PR merge mechanics, or application feature work.
GitHub is where developers evaluate your project before trying it. This skill covers README optimization, profile READMEs, discoverability through topics and awesome lists, and using GitHub features for marketing. Treat your GitHub presence as the first technical evaluation a developer performs — optimize accordingly.
When to Use
Use this skill when the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include:
"GitHub README"
"README optimization"
"GitHub profile"
"GitHub stars"
"GitHub discoverability"
"awesome lists"
"GitHub marketing"
Prerequisites
Read .agents/developer-audience-context.md if it exists — this file provides context about who evaluates the repository.
Audit your current GitHub presence (profile, pinned repos, READMEs) before making changes.
Confirm you have push access to the target repository or profile README repo.
Procedure
1. Audit Current Presence
Open the target repository on GitHub.
Review the existing README for structure, badges, quick start, and license.
Check repository settings for topics (up to 20 allowed).
Review the profile README if one exists (repo named exactly after the username).
Check Insights → Traffic for current views, clones, and referrers.
2. README Structure
A great README follows this anatomy:
Section
Purpose
Required?
Logo/Banner
Brand recognition, visual appeal
Recommended
Badges
Quick trust signals, status
Recommended
One-liner
What it does in one sentence
Required
Hero example
Immediate "what does it look like?"
Highly recommended
Features
Why use this over alternatives
Required
Quick start
Get running in < 2 minutes
Required
Installation
All installation methods
Required
Usage
Core usage examples
Required
Documentation
Link to full docs
Required
Contributing
How to contribute
Recommended
License
Legal clarity
Required
3. Apply the README Template
Use this template as a starting point. Replace placeholders with project-specific content:
# Tweet on new releasename:ReleaseAnnouncementon:release:types: [published]
jobs:announce:runs-on:ubuntu-lateststeps:-name:Tweetuses:ethomson/send-tweet-action@v1with:status:"🚀 ${{ github.repository }} ${{ github.event.release.tag_name }} released! ${{ github.event.release.html_url }}"consumer-key:${{secrets.TWITTER_CONSUMER_KEY}}# ... other secrets
Never commit live secrets. Use GitHub repository secrets (Settings → Secrets and variables → Actions) and reference them as ${{ secrets.YOUR_KEY }}. Example placeholders above are not real credentials.