FrancoStino/github-presence
bundled-skills/github-presence/SKILL.md
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 --global
skillsauthnpx skillsauth add FrancoStino/opencode-skills-antigravity github-presenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 27, 2026, 2:50 AM212.7s2 files scanned
SKILL.md
- 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:
- critical
- source:
- https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence
- source_repo:
- jonathimer/devmarketing-skills
- source_type:
- community
- date_added:
- 2026-07-01
- 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.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
<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
```bash
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
- Getting Started
- API Reference
- Examples
Contributing
We welcome contributions! Please see CONTRIBUTING.md for details.
License
MIT © Your Name
---
## 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.mdfile - 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, 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
Automated README Updates
# .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 "[email protected]"
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
# Auto-update GitHub stats image
- uses: lowlighter/metrics@latest
with:
token: ${{ secrets.METRICS_TOKEN }}
filename: github-metrics.svg
Release Announcements
# 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
- Join GitHub Sponsors (github.com/sponsors)
- Create compelling tier descriptions
- Set up funding.yml in repos
funding.yml example:
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 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
- Don't neglect the README — it's your landing page
- Don't use too many badges (cluttered)
- Don't let issues pile up unanswered
- Don't forget a license file
- Don't use low-quality or broken images
- Don't write walls of text without structure
- Don'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
- [ ] Clear, keyword-rich name and description
- [ ] Badges show CI status, version, license
- [ ] One-liner explains what it does
- [ ] Quick start gets users running in < 2 min
- [ ] Code examples are copy-pasteable
- [ ] All links work and are HTTPS
- [ ] Images have alt text
- [ ] Mobile-readable formatting
- [ ] License file present
- [ ] Contributing guidelines exist
- [ ] Topics are set (up to 20)
- [ ] Social preview image uploaded
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.
Related Skills
FrancoStino/llm-security
tools
VerifiedTrustedCommunity
Authorized security assessment of LLM applications and AI agents: prompt injection, tool abuse, RAG exposure, memory poisoning, system-prompt extraction, and agent-compliance engineering per OWASP LLM/ASI Top 10.
68SKILL.mdUpdated Aug 30, 2026
FrancoStino/liuguang-banlan-ui
development
VerifiedTrustedCommunity
Builds two parameterized UI modes—流光溢彩白 (iridescent white) and 五彩斑斓黑 (colorful black)—with OKLCH, WebGL/CSS fallback, vision gating, screenshot QA, and total/per-color intensity reports. Use when a UI request names either mode or needs measured color parameters.
68SKILL.mdUpdated Aug 30, 2026
FrancoStino/kimi-delegate
tools
VerifiedTrustedCommunity
Delegate coding tasks to the Kimi Code CLI (`kimi`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.
68SKILL.mdUpdated Aug 30, 2026
FrancoStino/js-reverse
development
VerifiedTrustedCommunity
Front-end JavaScript reverse engineering: locate signature chains, analyze encrypted request parameters, sample runtime behavior, and reproduce logic locally in Node for evidence-based output.
68SKILL.mdUpdated Aug 30, 2026