sickn33/agentic-awesome-skills/github-presence

Claude Code and agent skill by sickn33/agentic-awesome-skills

Trust tier 3
  • community
Source check pending

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-presence

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

  1. Read .agents/developer-audience-context.md if it exists
  2. Audit your current GitHub presence (profile, pinned repos, READMEs)
  3. Understand: GitHub is often the first technical evaluation — optimize accordingly

README Structure

The Anatomy of a Great README
SectionPurposeRequired?
Logo/BannerBrand recognition, visual appealRecommended
BadgesQuick trust signals, statusRecommended
One-linerWhat it does in one sentenceRequired
Hero exampleImmediate "what does it look like?"Highly recommended
FeaturesWhy use this over alternativesRequired
Quick startGet running in < 2 minutesRequired
InstallationAll installation methodsRequired
UsageCore usage examplesRequired
DocumentationLink to full docsRequired
ContributingHow to contributeRecommended
LicenseLegal clarityRequired
README Template
`markdown
<div align="center">
<img src="logo.svg" alt="Project Name" width="200">
<h1>Project Name</h1>
<p><strong>One compelling sentence explaining what this does.</strong></p>
<!-- Badges -->
<a href="https://github.com/org/repo/actions"><img src="https://github.com/org/repo/workflows/CI/badge.svg" alt="CI"></a>
<a href="https://www.npmjs.com/package/name"><img src="https://img.shields.io/npm/v/name.svg" alt="npm version"></a>
<a href="https://github.com/org/repo/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License"></a>
<a href="https://discord.gg/invite"><img src="https://img.shields.io/discord/123456789" alt="Discord"></a>
<br>
<br>
<a href="https://docs.example.com">Documentation</a> •
<a href="https://example.com">Website</a> •
<a href="https://discord.gg/invite">Discord</a>
</div>
---
## Why Project Name?
- **Feature 1** — Brief explanation
- **Feature 2** — Brief explanation
- **Feature 3** — Brief explanation
## Quick Start

npm install project-name

import { thing } from 'project-name';

const result = thing.doSomething(); console.log(result);

## Installation
### npm

npm install project-name

### yarn

yarn add project-name

### pnpm

pnpm add project-name

## Usage
### Basic Example

// Code example with comments

### Advanced Example

// More complex example

## Documentation
Full documentation available at [docs.example.com](https://docs.example.com)
- [Getting Started](https://docs.example.com/getting-started)
- [API Reference](https://docs.example.com/api)
- [Examples](https://docs.example.com/examples)
## Contributing
We welcome contributions! Link the project’s actual contribution guide here after confirming its path; this skill does not bundle one.
## License
MIT © [Your Name](https://yoursite.com)

Badges That Matter

Trust Signal Badges
BadgeWhat it showsWhen to use
CI/Build statusResult of the linked workflow, not overall qualityWhen meaningful
VersionLatest releaseAlways for packages
LicenseLegal clarityAlways
Downloads/installsAdoptionWhen impressive
CoverageExecuted lines/branches for the measured suite; not test qualityWhen current and accurately scoped
SecurityAudit statusIf you have it
Community Badges
BadgeSourcePurpose
Discord membersshields.ioShow active community
GitHub starsshields.ioSocial proof
Contributorsshields.ioOpen source health
Last commitshields.ioProject activity
Badge Services
ServiceURLBest for
Shields.ioshields.ioMost badges
Badgenbadgen.netFast, minimal
GitHub badgesNativeActions, issues
Badge Examples
markdown
<!-- Build status -->
![CI](https://github.com/org/repo/workflows/CI/badge.svg)
<!-- npm version -->
[![npm](https://img.shields.io/npm/v/package-name.svg)](https://www.npmjs.com/package/package-name)
<!-- Downloads -->
[![Downloads](https://img.shields.io/npm/dm/package-name.svg)](https://www.npmjs.com/package/package-name)
<!-- License -->
[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
<!-- Discord -->
[![Discord](https://img.shields.io/discord/SERVER_ID?color=7289da&logo=discord&logoColor=white)](https://discord.gg/invite)
<!-- Stars -->
[![GitHub stars](https://img.shields.io/github/stars/org/repo?style=social)](https://github.com/org/repo)

Profile README

Setting Up Profile README
  1. Create a repository with your username (e.g., github.com/yourname/yourname)
  2. Make that repository public and add nonempty README.md at its root.
  3. GitHub displays it on eligible personal profiles; managed user accounts do not support profile READMEs.
Profile README Structure
markdown
# Hi, I'm [Name] 👋
[One sentence about what you do]
## What I'm Working On
-🔭 Building [project] — [brief description]
-🌱 Learning [technology]
-💬 Ask me about [expertise areas]
## Projects
| Project | Description | Stars |
|---------|-------------|-------|
| [Project 1](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/link) | Brief description | ![Stars](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/badge) |
| [Project 2](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/link) | Brief description | ![Stars](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/badge) |
## Recent Blog Posts
<!-- BLOG-POST-LIST:START -->
<!-- Automated with GitHub Actions -->
<!-- BLOG-POST-LIST:END -->
## Connect
[![Twitter](https://img.shields.io/badge/-Twitter-1DA1F2?style=flat&logo=twitter&logoColor=white)](https://twitter.com/handle)
[![LinkedIn](https://img.shields.io/badge/-LinkedIn-0077B5?style=flat&logo=linkedin&logoColor=white)](https://linkedin.com/in/handle)
## GitHub Stats
![Your GitHub stats](https://github-readme-stats.vercel.app/api?username=yourusername&show_icons=true)
Profile README Best Practices
DoDon't
Keep it scannableWrite paragraphs
Show your best projectsList everything
Include current workLet it get stale
Add contact methodsMake it hard to reach you
Show personalityBe generic

Discoverability

GitHub Topics

Topics are how people find repositories. Optimize for search.

Topic strategyExample
Technologyjavascript, rust, python
Frameworkreact, nextjs, django
Use casecli, api, testing
Categorydeveloper-tools, devops
Problemauthentication, caching

Add topics: Repository settings → Topics (up to 20)

Search Optimization

GitHub search considers:

  1. Repository name — Include main keyword
  2. Description — 350 chars, keyword-rich
  3. README content — Full text indexed
  4. Topics — Category matching
  5. Language — Auto-detected
Awesome Lists

Getting on awesome lists drives traffic and credibility.

StepAction
1Find relevant awesome lists (search "awesome + [topic]")
2Check list requirements (quality, activity, docs)
3Ensure your project meets criteria
4Submit PR following list's guidelines
5Be patient — curation takes time

Popular awesome lists for dev tools:

  • awesome-cli-apps
  • awesome-selfhosted
  • awesome-nodejs
  • awesome-python
  • awesome-go
  • awesome-rust
  • awesome-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
yaml
# .github/workflows/readme-update.yml
name: Update README
on:
schedule:
- cron: '0 0 * * *' # Daily
workflow_dispatch:
jobs:
update:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
# Example: Update blog post list
- uses: gautamkrishnar/blog-post-workflow@master
with:
feed_list: "https://yourblog.com/feed"
- name: Commit changes
run: |
git config --local user.email "action@github.com"
git config --local user.name "GitHub Action"
git add -- README.md
git diff --quiet && git diff --staged --quiet || git commit -m "Update README"
# Open a reviewed topic-branch PR through the repository’s approved process.
# Do not push this scheduled job directly to a protected default branch.
Metrics and Stats
yaml
# Auto-update GitHub stats image
- uses: lowlighter/metrics@latest
with:
token: ${{ secrets.METRICS_TOKEN }}
filename: github-metrics.svg
Release Announcements
yaml
# Tweet on new release
name: Release Announcement
on:
release:
types: [published]
jobs:
announce:
runs-on: ubuntu-latest
steps:
- name: Tweet
uses: ethomson/send-tweet-action@v1
with:
status: "🚀 ${{ github.repository }} ${{ github.event.release.tag_name }} released! ${{ github.event.release.html_url }}"
consumer-key: ${{ secrets.TWITTER_CONSUMER_KEY }}
# ... other secrets

GitHub Sponsors

Setting Up Sponsors
  1. Join GitHub Sponsors (github.com/sponsors)
  2. Create compelling tier descriptions
  3. Set up funding.yml in repos

funding.yml example:

yaml
github: [yourusername]
patreon: yourpatreon
open_collective: yourproject
ko_fi: yourkofi
custom: ["https://buymeacoffee.com/you"]
Sponsor Tiers That Work
TierPriceOffer
Supporter$5/moThanks + name in README
Backer$15/moLogo in README + Discord role
Sponsor$50/moPriority support + feature voting
Enterprise$200+/moDedicated support + consultation

Platform-Specific Do's and Don'ts

Do's
  1. Do optimize your README for first impression
  2. Do use badges for quick trust signals
  3. Do add relevant topics (up to 20)
  4. Do keep your profile README current
  5. Do respond to issues and PRs promptly
  6. Do pin your best repositories
  7. Do include clear installation instructions
  8. 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

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
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/sickn33/agentic-awesome-skills/github-presence/badge)](https://verified-skill.com/skills/sickn33/agentic-awesome-skills/github-presence)

Something wrong with this skill or its page? Tell us.