Guides GitHub for parasite SEO, GEO (AI citation), and curated list creation. GitHub is a Tier 2 Technical Authority platform—high domain authority, fast indexing, very high AI citation probability. Use for repos, README, GitHub Pages, gists, and Awesome-style navigation lists.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongithubExecute the skills CLI command in your project's root directory to begin installation:
Fetches github from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate github. Access via /github in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
Guides GitHub for parasite SEO, GEO (AI citation), and curated list creation. GitHub is a Tier 2 Technical Authority platform—high domain authority, fast indexing, very high AI citation probability. Use for repos, README, GitHub Pages, gists, and Awesome-style navigation lists.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
| Factor | Effect |
|---|---|
| Domain authority | High DA; repos, gists, Pages rank well |
| Fast indexing | Search engines crawl GitHub frequently |
| AI citation | ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO framework |
| Technical expertise | Strong expertise signals; structured docs become AI reference material |
| Cross-platform | Share across Dev.to, Stack Overflow, forums; amplifies visibility |
| Use case | Format | Purpose |
|---|---|---|
| Parasite SEO | Repos, README, Pages, gists | Leverage GitHub authority for rankings and backlinks |
| GEO | Documentation, tutorials, curated lists | AI tools cite GitHub for technical answers |
| Curated / navigation lists | Awesome-style repos | Topic-specific resource directories; backlinks, discovery |
Ranking weight (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high.
| Practice | Guideline |
|---|---|
| Descriptive | Hint at what the project does |
| Keyword-rich | Include primary keywords (markdown-editor not my-project) |
| Hyphens | Separate words (react-component-library) |
| Concise | Shorter = memorable, shareable |
| Limit | Guideline |
|---|---|
| 350 chars | Hard limit; GitHub enforces |
| ~128 chars | Optimal for brevity; often displayed fully |
| Content | Primary keyword + natural variations; what it does, who it's for; link to website or docs if space |
Example: "A fast, lightweight markdown editor for React with live preview, syntax highlighting, and export to PDF. Built with TypeScript."
| Limit | Guideline |
|---|---|
| 6–20 topics | Max 20; 6–10 recommended |
| ~50 chars each | Per topic |
| Format | Lowercase, hyphens, numbers only |
| Mix | Technology (react, python), purpose (cli, library), category (seo, ai-tools), community (hacktoberfest) |
Underutilized but highly effective for discoverability and GEO.
| Section | Purpose | SEO/GEO |
|---|---|---|
| Title + tagline | H1 + 1–2 sentence summary; keywords in first paragraph | Critical; first 100 words weighted |
| Table of contents | Links to H2/H3; for READMEs >500 words | Navigation; crawlability |
| Installation / Quick start | Prerequisites; exact commands; copy-paste ready | Use-case clarity |
| Usage examples | Code blocks; common scenarios | Citable; extractable |
| Screenshots / GIFs | Demo, output; alt text required | Engagement; accessibility |
| Badges | Build, version, license | Trust signals |
| Contributing | Link to CONTRIBUTING.md | Community signal |
| License | Link to LICENSE | Completeness |
Word count: No hard limit; 500–1,500 words typical for product repos. Lead with value; expand later.
| Practice | Guideline |
|---|---|
| Answer-first | Direct answer in first 1–2 sentences (40–60 words) |
| Short paragraphs | 2–3 sentences max; extractable clarity |
| Question-style headings | H2/H3 as questions where relevant |
| Data inclusion | Stats, numbers; cited content ~40% more likely to include data |
| Freshness | Update regularly; ~76% of cited content updated within 30 days |
Entity signals: Clear project name, author, maintainer; consistent identity. See entity-seo.
| Surface | Use |
|---|---|
| README | Landing page for repo; keyword-optimized summary, headings, links |
| GitHub Pages | Static site; blog, FAQ, docs; additional ranking opportunities |
| Gists | Micro-content; long-tail keywords; link to repos or external resources |
| Wiki | Keyword-rich documentation |
| Issues | Q&A, discussions; indexable |
| Element | Practice |
|---|---|
| Repository title | Primary keywords; descriptive; hyphens |
| About | 350 chars max; keyword-rich; primary keyword + natural variations |
| Description | Secondary keywords; link to website or resources |
| README | Keyword-optimized summary first; headings, bullet points; screenshots; links to docs, tutorials |
| Topics / tags | 6–20 relevant topics; 50 chars each |
| GitHub Pages | Mobile-friendly; metadata; blog/FAQ for extra keywords |
| Factor | Practice |
|---|---|
| README clarity | Clear, citable paragraphs; direct answers |
| Documentation | Structured; AI tools parse well |
| Entity signals | Clear project, author identity; see entity-seo |
| Consistency | Active maintenance; engagement (stars, forks, watchers) |
Awesome lists = Curated, topic-specific resource lists on GitHub. Function like navigation directories; high traffic, backlinks, discovery. sindresorhus/awesome (441K+ stars) is the master list; 6,500+ curated lists exist across topics.
| Category | Examples |
|---|---|
| Master list | sindresorhus/awesome — hub of all awesome lists |
| SEO / Marketing | awesome-seo, awesome-ai-seo, bmpi-dev/awesome-seo |
| AI / ML | awesome-ai-tools, AITreasureBox, awesome-ai |
| Dev tools | awesome-tools, awesome-cli, awesome-nodejs |
| Languages | awesome-python, awesome-javascript, awesome-go |
| Frontend / Backend | awesome-react, awesome-vue, awesome-django |
| Other | awesome-security, awesome-gaming, awesome-databases |
| Element | Practice |
|---|---|
| Title | Clear, focused (e.g., "Awesome SEO," "Awesome AI Tools") |
| Description | Succinct; scope clear |
| Sections | Categorized (e.g., Tutorials, Tools, Articles) |
| Items | Curated, not collected; only include what you recommend |
| Item format | - [Name](URL) - Brief description of why it's awesome |
| License | CC0 or similar |
| Contributing | contributing.md for PR process |
| Action | Use |
|---|---|
| Submit to existing list | PR to awesome-* repos; follow list format; contact maintainer |
| Create new list | When no list exists for your niche; follow awesome guidelines |
| Link between lists | Link to other awesome lists that cover subjects better |
| Mistake | Avoid |
|---|---|
| Ignoring engagement | Not responding to issues/PRs reduces trust |
| Irregular updates | Outdated repos signal inactivity |
| Incomplete docs | Lack of clear descriptions frustrates users |
| Generic titles | Missing keywords reduces discoverability |
| Thin awesome lists | Low-quality or uncurated items hurt credibility |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
github is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend github for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: github is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added github from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in github — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: github is the kind of skill you can hand to a new teammate without a long onboarding doc.
github is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
github has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for github matched our evaluation — installs cleanly and behaves as described in the markdown.
github fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 28