sickn33/agentic-awesome-skills/github-presence
Claude Code and agent skill by sickn33/agentic-awesome-skills
- community
Checking that the SKILL.md file is still in the repository.
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," or "GitHub marketing."
Install
npx vskill@latest install sickn33/agentic-awesome-skills/github-presenceSKILL.md
GitHub Presence
When to Use
Use this skill when you need 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," or "GitHub marketing.".
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.
Before You Start
- Read
.agents/developer-audience-context.mdif it exists - Audit your current GitHub presence (profile, pinned repos, READMEs)
- Understand: GitHub is often the first technical evaluation — optimize accordingly
README Structure
The Anatomy of a Great README
| 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 |
README Template
npm install project-name
import { thing } from 'project-name';
const result = thing.doSomething(); console.log(result);
npm install project-name
yarn add project-name
pnpm add project-name
// Code example with comments
// More complex example
Badges That Matter
Trust Signal Badges
| Badge | What it shows | When to use | |
|---|---|---|---|
| CI/Build status | Result of the linked workflow, not overall quality | When meaningful | |
| Version | Latest release | Always for packages | |
| License | Legal clarity | Always | |
| Downloads/installs | Adoption | When impressive | |
| Coverage | Executed lines/branches for the measured suite; not test quality | When current and accurately scoped | |
| Security | Audit status | If you have it |
Community Badges
| Badge | Source | Purpose | |
|---|---|---|---|
| Discord members | shields.io | Show active community | |
| GitHub stars | shields.io | Social proof | |
| Contributors | shields.io | Open source health | |
| Last commit | shields.io | Project activity |
Badge Services
| Service | URL | Best for | |
|---|---|---|---|
| Shields.io | shields.io | Most badges | |
| Badgen | badgen.net | Fast, minimal | |
| GitHub badges | Native | Actions, issues |
Badge Examples
Profile README
Setting Up Profile README
- Create a repository with your username (e.g.,
github.com/yourname/yourname) - Make that repository public and add nonempty
README.mdat its root. - GitHub displays it on eligible personal profiles; managed user accounts do not support profile READMEs.
Profile README Structure
Profile README Best Practices
| Do | Don't | |
|---|---|---|
| Keep it scannable | Write paragraphs | |
| Show your best projects | List everything | |
| Include current work | Let it get stale | |
| Add contact methods | Make it hard to reach you | |
| Show personality | Be generic |
Discoverability
GitHub Topics
Topics are how people find repositories. Optimize for search.
| Topic strategy | Example | |
|---|---|---|
| Technology | javascript, rust, python | |
| Framework | react, nextjs, django | |
| Use case | cli, api, testing | |
| Category | developer-tools, devops | |
| Problem | authentication, caching |
Add topics: Repository settings → Topics (up to 20)
Search Optimization
GitHub search considers:
- Repository name — Include main keyword
- Description — 350 chars, keyword-rich
- README content — Full text indexed
- Topics — Category matching
- Language — Auto-detected
Awesome Lists
Getting on awesome lists drives traffic and credibility.
| Step | Action | |
|---|---|---|
| 1 | Find relevant awesome lists (search "awesome + [topic]") | |
| 2 | Check list requirements (quality, activity, docs) | |
| 3 | Ensure your project meets criteria | |
| 4 | Submit PR following list's guidelines | |
| 5 | Be patient — curation takes time |
Popular awesome lists for dev tools:
awesome-cli-appsawesome-selfhostedawesome-nodejsawesome-pythonawesome-goawesome-rustawesome-devops
GitHub Actions for Marketing
Automation examples need adaptation, not direct installation: review each third-party action and pin its full verified commit SHA (floating master/latest tags below are placeholders). Grant minimum token permissions and avoid passing secrets to untrusted actions. Use a topic-branch PR for README changes where branch protection requires it; never bypass protections or publish posts, sponsorship terms or external PRs without authorization. A stats embed is an external service, not proof of usage. Use actual project license/links rather than copying MIT or upstream template URLs.
Repository traffic covers a rolling 14-day window in UTC; export dated aggregates when longer comparisons are needed. Full clones are not fetches and are not unique installs.
Automated README Updates
Metrics and Stats
Release Announcements
GitHub Sponsors
Setting Up Sponsors
- Join GitHub Sponsors (github.com/sponsors)
- Create compelling tier descriptions
- Set up funding.yml in repos
funding.yml example:
Sponsor Tiers That Work
| Tier | Price | Offer | |
|---|---|---|---|
| Supporter | $5/mo | Thanks + name in README | |
| Backer | $15/mo | Logo in README + Discord role | |
| Sponsor | $50/mo | Priority support + feature voting | |
| Enterprise | $200+/mo | Dedicated support + consultation |
Platform-Specific Do's and Don'ts
Do's
- Do optimize your README for first impression
- Do use badges for quick trust signals
- Do add relevant topics (up to 20)
- Do keep your profile README current
- Do respond to issues and PRs promptly
- Do pin your best repositories
- Do include clear installation instructions
- Do submit to relevant awesome lists
Don'ts
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/github-presence/SKILL.md
Popularity
- Repository stars
- 47,054
- Repository forks
- 6,853
- 7-day trend score
- 54
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/sickn33/agentic-awesome-skills/github-presence)