Skip to main content ホーム クリエイター chonsong skill-retriever github-presence
github-presence 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."
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ChonSong/skill-retriever --skill github-presenceコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... このリポジトリの他の Skills AI-powered Draw.io diagram generation with real-time browser preview. Create flowcharts, architecture diagrams, sequence diagrams, and cloud infrastructure diagrams (AWS/GCP/Azure) using natural language. Supports animated connectors, real-time editing, and structured A–H format extraction from text or images.
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention. Features Task tool for subagent dispatch, parallel code review with 3 specialized reviewers, severity-based issue triage, distributed task queue with dead letter handling, automatic deployment to cloud providers, A/B testing, customer feedback loops, incident response, circuit breakers, and self-healing. Handles rate limits via distributed state checkpoints and auto-resume with exponential backoff. Requires --dangerously-skip-permissions flag.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this,"...
name github-presence description 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." risk unknown source https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence source_repo jonathimer/devmarketing-skills source_type community date_added 2026-07-01T00:00:00.000Z license MIT license_source https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
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.md if 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
<div align = "center"
<img src ="logo.svg" alt ="Project Name" width ="200" >
<h1 >
</h1 >
<p >
<strong >
</strong >
</p >
<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" >
</a >
<a href ="https://example.com" >
</a >
<a href ="https://discord.gg/invite" >
</a >
</div >
## Why Project Name?
-
**Feature 1**
-
**Feature 2**
-
**Feature 3**
## Quick Start
```bash
npm install project-name
import { thing } from 'project-name' ;
const result = thing.doSomething ();
console .log (result);
Installation
npm
yarn
pnpm
Usage
Basic Example
Advanced Example
Documentation
Contributing
License
---
## Badges That Matter
### Trust Signal Badges
| Badge | What it shows | When to use |
|-------|--------------|-------------|
| CI/Build status | Code quality | Always |
| Version | Latest release | Always for packages |
| License | Legal clarity | Always |
| Downloads/installs | Adoption | When impressive |
| Coverage | Test quality | If > 70% |
| 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
```markdown
<!-- Build status -->
<!-- npm version -->
[](https://www.npmjs.com/package/package-name)
<!-- Downloads -->
[](https://www.npmjs.com/package/package-name)
<!-- License -->
[](LICENSE)
<!-- Discord -->
[](https://discord.gg/invite)
<!-- Stars -->
[](https://github.com/org/repo)
Profile README
Setting Up Profile README
Create a repository with your username (e.g., github.com/yourname/yourname)
Add a README.md file
This displays on your profile page
Profile README Structure # 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 |  |
| [Project 2 ](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/link ) | Brief description |  |
## Recent Blog Posts
<!-- BLOG-POST-LIST:START -->
<!-- Automated with GitHub Actions -->
<!-- BLOG-POST-LIST:END -->
## Connect
[](https://twitter.com/handle )
[](https://linkedin.com/in/handle )
## GitHub Stats
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, pythonFramework react, nextjs, djangoUse case cli, api, testingCategory developer-tools, devopsProblem authentication, caching
Add topics : Repository settings → Topics (up to 20)
Search Optimization
Repository name — Include main keywordDescription — 350 chars, keyword-richREADME content — Full text indexedTopics — Category matchingLanguage — 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
Automated README Updates
name: Update README
on:
schedule:
- cron: '0 0 * * *'
workflow_dispatch:
jobs:
update:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- 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 -A
git diff --quiet && git diff --staged --quiet || git commit -m "Update README"
git push
Metrics and Stats
- uses: lowlighter/metrics@latest
with:
token: ${{ secrets.METRICS_TOKEN }}
filename: github-metrics.svg
Release Announcements
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 }}
GitHub Sponsors
Setting Up Sponsors
Join GitHub Sponsors (github.com/sponsors)
Create compelling tier descriptions
Set up funding.yml in repos
github: [yourusername ]
patreon: yourpatreon
open_collective: yourproject
ko_fi: yourkofi
custom: ["https://buymeacoffee.com/you" ]
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 impressionDo use badges for quick trust signalsDo add relevant topics (up to 20)Do keep your profile README currentDo respond to issues and PRs promptlyDo pin your best repositoriesDo include clear installation instructionsDo submit to relevant awesome lists
Don'ts
Don't neglect the README — it's your landing pageDon't use too many badges (cluttered)Don't let issues pile up unansweredDon't forget a license fileDon't use low-quality or broken imagesDon't write walls of text without structureDon't ignore contribution guidelines
Measuring Success
GitHub Metrics to Track Metric What it tells you Goal Stars Interest/bookmarks Growth over time Forks Active usage Quality > quantity Clones People trying it Pre-install interest Traffic Profile/repo views Awareness Referrers Where traffic comes from Channel effectiveness Contributors Community health Sustainable project
Traffic Insights Access via: Repository → Insights → Traffic
Views and unique visitors
Popular content (which files)
Referring sites
Clone activity
Tools Tool Use case Octolens Monitor GitHub for mentions of your project, competitors, and relevant discussions. Get alerts when people talk about problems you solve. Shields.io Generate status badges GitHub Readme Stats Dynamic stats for profile Carbon Beautiful code screenshots readme.so README generator Metrics Advanced profile stats
README Audit Checklist
Related Skills
developer-audience-context — Know who evaluates your repohacker-news-strategy — HN users check GitHub before upvotingreddit-engagement — Redditors evaluate via GitHubdev-to-hashnode — Link from README to content
Limitations
Use this skill only when the task clearly matches its upstream source and local project context.
Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
