Docs Seeker
einverne/dotfiles
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration.
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists.
Install GitHub
$ npx skills add kostja94/marketing-skills --skill github -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kostja94/marketing-skills github --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/platforms/github .claude/skills/github && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "github" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/platforms/github into .claude/skills/github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kostja94/marketing-skills/tree/main/skills/platforms/githubType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kostja94/marketing-skills --skill github -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kostja94/marketing-skills github --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/platforms/github .agents/skills/github && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/platforms/github into .agents/skills/github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill github -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kostja94/marketing-skills github --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/platforms/github .cursor/skills/github && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "github" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/platforms/github into .cursor/skills/github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kostja94/marketing-skills.git --path skills/platforms/github--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kostja94/marketing-skills --skill github -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kostja94/marketing-skills github --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/platforms/github .gemini/skills/github && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "github" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/platforms/github into .gemini/skills/github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kostja94/marketing-skills githubInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kostja94/marketing-skills --skill github -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/platforms/github .github/skills/github && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "github" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/platforms/github into .github/skills/github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill github -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kostja94/marketing-skills github --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/platforms/github .opencode/skills/github && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "github" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/platforms/github into .opencode/skills/github/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
github- GitHub stars
- 1k
- Token cost
- ~4.5k tokens
- SKILL.md length
- 1,918 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists.
- Works in 5 steps: Title + answer-first tagline (+ slim… → ### What I do — identity, proof link(s),… → ### Open source — bold repo links +… → …
- Wants to use GitHub for SEO
- SKILL.md covers Why GitHub for SEO, Use Cases, Surfaces: profile vs repository and Repository home: layout map, plus 7 more sections
- Calls npx; reaches username.github.io
What it does
GitHub is an agent skill from kostja94/marketing-skills. When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation…
Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Technical documentation, Product strategy and AI search optimization. It works with GitHub. The repository describes itself as: Agent Skills for Marketing — SEO, Social, Influencer & More. 160+ open-source skills for SEO, content, 40+ page types, paid ads, channels, and strategies. Add project context… The licence is MIT.
When your agent uses it
- Wants to use GitHub for SEO
- Open source marketing
- README optimization
- Curated Awesome lists
Example prompts
- “GitHub,”
- “GitHub SEO,”
- “GitHub parasite SEO,”
- “/github”
Requirements
- Node.js
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Title + answer-first tagline (+ slim badge row).
- ### What I do — identity, proof link(s), without repeating the same URLs again later.
- ### Open source — bold repo links + pitches + optional one code fence.
- ### Find me — single line of deduped links (site · bio · cases · social · email).
- ### Activity (optional) — small github-readme-stats + star-history; alt text on .
What it can do on your machine
Read from SKILL.md and the folder at commit 8dd89c5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
username.github.io
Also links to:
docs.github.comgithub.comstar-history.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GitHub loads about 4.5k tokens when it runs. Until then it costs about 165 tokens; SKILL.md has 1,918 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from kostja94/marketing-skills at commit 8dd89c5, republished under its MIT licence (© kostja94). 1,918 words, ~4,510 tokens.
Download SKILL.mdSave it as
.claude/skills/github/SKILL.md (or your agent's skills folder).- name
- github
- description
- When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy.
- metadata.version
- 1.5.0
Platforms: GitHub
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.
Why GitHub for SEO
| 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 Cases
| 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 |
Surfaces: profile vs repository
| Surface | What it is | Optimization focus |
|---|---|---|
| Profile README | Public repo with the same name as the username; root README.md renders on the profile | Personal brand, flagship links, social proof |
| Pinned | Up to 6 repos or gists on the profile | Showcase top projects; align with entity signals (entity-seo) |
| Per-repo README | Root README.md on each repo’s Code tab | Product landing; install, proof, CTAs |
Changing a normal repo README does not change the profile banner unless that content is the profile README repo or linked from it.
Profile README (username/username)
Not the same as a product repo README. Optimize for identity + navigation in ~15–40 lines of rendered content unless the user explicitly wants a long-form CV. Official setup: Managing your profile README.
| Principle | Do | Avoid |
|---|---|---|
| Length | Short, scannable sections; omit ToC unless the file is genuinely long | Applying “500–1,500 words typical for product repos” here |
| Headings | ### blocks (e.g. What I do · Open source · Find me) for fast eyeballing | Many nested ## + long narrative without breaks |
| Links | Each primary URL once in a Find me / Connect line (or badges or a slim table—not all three repeating the same destinations) | Duplicate site/LinkedIn/email in badges, tables, and prose |
| Repos block | Bold repo name + ≤2 short lines + at most one copy-paste command (e.g. npx skills add …) — same scan pattern popular profiles use for “flagship OSS” without cloning the repo’s full README | Full feature matrices, changelog, or install docs pasted into the profile file |
| Layout | Optional centered header (<div align="center">) for name + tagline + badges only; body stays left-aligned markdown for readability | Center-wrapping the entire README |
| Optional widgets | Compact Shields (flat style); optional github-readme-stats / star-history — third-party, treat as conversion/social proof, not core SEO | Wall of for-the-badge badges when the same CTAs are repeated in text |
Minimal outline (typical profile):
- Title + answer-first tagline (+ slim badge row).
### What I do— identity, proof link(s), without repeating the same URLs again later.### Open source— bold repo links + pitches + optional one code fence.### Find me— single line of deduped links (site · bio · cases · social · email).### Activity(optional) — small github-readme-stats + star-history; alt text on<img>.
Reference pattern (high-signal, low-noise): scan-first profiles such as alchaincyf — short ### blocks, bold product/repo names, one “find me” cluster.
Entity hub pattern: When the person has a canonical site, lead with it in the opening line and mirror the same URL in Pinned / profile About (if used) so site ↔ GitHub OSS stay aligned for entity-seo.
Profile README checklist (short)
- H1 + one answer-first tagline (keywords: role, stack, domain)
- Canonical outbound links (site, social, email) deduplicated
- Pinned repos (≤6) match the story told in the README
- Optional: Activity section — group stats / star-history under one heading instead of scattering widgets
- Last updated footnote for freshness (GEO signal)
Repository home: layout map
| Area | Typical contents | SEO / ops note |
|---|---|---|
| Main column | File list; rendered root README below | First screen and H2/H3 carry most narrative |
| About sidebar | Description, Website, Topics, releases shortcut, license, languages | Keep Description and README first paragraph consistent; Website should match the primary outbound CTA |
| Other tabs | Issues, PRs, Actions, etc. | Engagement and freshness signals |
Website field: Maintained via repo Settings / About edit; prefer one canonical docs or product URL aligned with README links.
In-site discovery (high level)
| Entry | Role | Caveat |
|---|---|---|
| Trending | Time-windowed visibility | Formula is not public; never promise ranking |
| Explore | Collections, themes, programs | Useful for patterns and seasonal campaigns |
| Topics | Topic pages tied to repository topics | Aligns with Topics metadata (see Topics section below) |
| Search | Query across repos and users | README + About + topics drive match quality |
UI and URLs evolve; verify on github.com.
flowchart LR
discovery[Discovery or referral]
home[Repository home]
readme[README and About]
outbound[Site or docs]
discovery --> home
home --> readme
readme --> outboundRepository Name, About & README (SEO/GEO Priority)
Ranking weight (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high.
Repository Name
| 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 |
About Section (Description)
| 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."
Topics
| 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.
README Structure & Components
Targets repository (project) READMEs unless noted. Profile README overrides: shorter, fewer sections—see Profile README (username/username) above.
| 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 long repo READMEs (often >500 words). Usually skip on profile README | 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 / library repos. Lead with value; expand later. Profile README: prefer dense brevity—long-form belongs on the canonical site or in pinned repos’ own READMEs.
README GEO / AI Citation
| Practice | Guideline |
|---|---|
| Answer-first | Direct answer in first 1–2 sentences (40–60 words); profile README may compress to one punchy tagline under H1 if outbound links carry the rest |
| Short paragraphs | 2–3 sentences max; extractable clarity |
| Question-style headings | H2/H3 as questions where relevant (repository READMEs); on profile README, optional — clarity of sections matters more than question phrasing |
| 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.
Show full SKILL.md (782 more words)Show less
README Checklist — repository (default)
- Project title with keywords
- Concise description in first paragraph
- H2/H3 structure; alt text for images
- Installation + usage examples
- Screenshots or demo
- Badges; Contributing; License
- Internal links to related docs/repos
- 6–20 topics on repo
(For profile username/username, use the shorter Profile README checklist under Surfaces—not every row above applies.)
Parasite SEO on GitHub
Key Surfaces
| 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 |
GitHub Pages vs README
| Surface | Role |
|---|---|
| README | First impression; Stars/forks; short pitch and deep links |
| Pages | Multi-page static site: long docs, blog, changelog |
Default URL patterns: A user or organization site often uses a username.github.io repository and serves at https://username.github.io. A project site is published from a given repo and typically appears at https://username.github.io/repository/ (path may vary with settings). See About GitHub Pages.
Limits: Build size, bandwidth, and build-frequency caps change over time—cite GitHub Pages limits when users need numbers, not hard-coded figures from this skill.
Optimization
| 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 |
Gists for Micro-Content
- Target specific long-tail keywords
- Link back to larger repos or external resources
- Share code snippets, small utilities
Community Engagement
- Respond to issues and PRs; builds trust
- Contribute to popular projects; backlinks, visibility
- Keep repos updated; outdated = lower credibility
GEO on GitHub
| 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) |
Repository archetypes
| Archetype | Intent | First-screen emphasis |
|---|---|---|
| Product / library | Installable software, SDK, CLI, service | Install, quickstart, proof (CI, license), support path |
| Curated / resource | Awesome-style lists, indexes | Scope, curation bar, contribution rules |
| Personal profile hub | Public username/username README on the profile | Identity + canonical links + pinned flagship repos; no duplication of full product READMEs |
Match metrics to type: curated lists optimize for trust and backlinks; product repos optimize for adoption and issue quality.
Curated / Navigation Lists (Awesome-Style)
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.
Examples by Category
| 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 |
When to Create
- You have a niche with many quality resources to curate
- Existing lists lack coverage of your topic
- You want a backlink asset and topical authority
List Structure (sindresorhus/awesome guidelines)
| 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 |
Getting Listed vs. Creating
| 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 |
Discovery
- sindresorhus/awesome — Master list of awesome lists
- AwesomeSearch — Search across awesome lists
- more-awesome — Directory of awesome lists
Common Mistakes
| 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 |
| Profile README = product README | Pasting install/Contributing/screenshot-heavy templates on username/username — use the profile checklist |
| Link sprawl on profile | Same homepage/social/email repeated in badges, tables, and long copy — consolidate |
Output Format
- Use case (parasite SEO / GEO / curated list)
- Surface scope (profile vs specific repository; README vs Pages)
- Repository name, About, Topics (if optimizing metadata)
- Surface (README, Pages, gist, awesome repo)
- README structure (sections, word count, GEO practices if applicable) — if profile README, cite short outline + deduped links + optional widgets per Profile README section above
- Optimization (keywords, structure, links)
- Ready-to-use copy or structure where applicable
Related Skills
- parasite-seo: Parasite SEO strategy; GitHub as Tier 2 technical platform
- generative-engine-optimization: GEO strategy; GitHub for AI citation
- open-source-strategy: Open source commercialization; GitHub as primary distribution
- directory-submission: Directory and curated list submission; awesome lists as curated lists
- link-building: GitHub as link acquisition; repos, gists, awesome lists
- entity-seo: Entity signals (project, author); Organization, Person
© kostja94, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/platforms/github of kostja94/marketing-skills.
Open the folder on GitHubat commit 8dd89c5
Compare with similar skills
GitHub next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitHub this skillkostja94/marketing-skills | 1k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Docs Seekereinverne/dotfiles | 121 | 1 repos | ~1.4k | Automated safety check: Pass | GPL-3.0 | |
| GitHub Readmethatrebeccarae/claude-marketing | 162 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Founder Led ContentAIDevGTM/gtm-cofounder | 310 | — | ~998 | Automated safety check: Pass | MIT | |
| LLM Docs OptimizerSidiora-Labs/centra-llm-agents | 115 | — | ~5.4k | Automated safety check: Pass | Custom licence | |
| Skill Personalizerhqhq1025/skill-optimizer | 180 | — | ~630 | Automated safety check: Pass | MIT |
Similar skills
GitHub Readme
thatrebeccarae/claude-marketing
Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance.
Founder Led Content
AIDevGTM/gtm-cofounder
Build authority by teaching the problem space, not announcing features.
LLM Docs Optimizer
Sidiora-Labs/centra-llm-agents
Optimize documentation for AI coding assistants and LLMs. An agent skill from Sidiora-Labs/centra-llm-agents.
Skill Personalizer
hqhq1025/skill-optimizer
A skill your agent uses when auditing or adapting newly created, downloaded, forked, installed, or community Agent Skills to the user's tools, habits, directories, session history, and preferred…
Build Backlinks
onvoyage-ai/gtm-engineer-skills
Finds free backlink and brand mention opportunities across Hacker News, Quora, GitHub, directories, and niche communities.
More from kostja94/marketing-skills
All 102 skills in this repoGrokipedia Recommendations
kostja94/marketing-skills
When the user wants to add recommendations, links, or content to Grokipedia.
AI Traffic Tracking
kostja94/marketing-skills
When the user wants to track AI search traffic in GA4 or GSC.
Analytics Tracking
kostja94/marketing-skills
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions).
Brand Visual Generator
kostja94/marketing-skills
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics).
Canonical Tag
kostja94/marketing-skills
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals.
Content Strategy
kostja94/marketing-skills
When the user wants to plan content for SEO, create content calendar, or build topic clusters.
Related
Works with
Categories
Questions about GitHub
What does GitHub do?
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. GitHub is an agent skill from kostja94/marketing-skills. When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists.
When should I use GitHub?
GitHub fits situations like: wants to use GitHub for SEO; open source marketing; README optimization; curated Awesome lists.
How do I install GitHub in Claude Code?
Run `npx skills add kostja94/marketing-skills --skill github -a claude-code`. Or copy the skill folder (skills/platforms/github in kostja94/marketing-skills) into .claude/skills/github in your project. Claude Code loads it when a task matches its description.
How do I install GitHub in Codex?
Run `npx skills add kostja94/marketing-skills --skill github -a codex`. Or copy the skill folder (skills/platforms/github in kostja94/marketing-skills) into .agents/skills/github in your project. Codex loads it when a task matches its description.
Can I use GitHub in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kostja94/marketing-skills --skill github -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github, .gemini/skills/github, .github/skills/github and .opencode/skills/github in your project.
What does GitHub need to run?
Going by SKILL.md and its folder, GitHub needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does GitHub access the network?
SKILL.md names 4 domains. In commands or code: username.github.io; the agent is likely to contact it when it follows the instructions. As links in the text: docs.github.com, github.com and star-history.com. This is read from the text; nothing was executed.
Is GitHub safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does GitHub use?
GitHub is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub use?
About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GitHub?
Skills that share tags, products or a category with GitHub: Docs Seeker (einverne/dotfiles, 121 stars), GitHub Readme (thatrebeccarae/claude-marketing, 162 stars), Founder Led Content (AIDevGTM/gtm-cofounder, 310 stars) and LLM Docs Optimizer (Sidiora-Labs/centra-llm-agents, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub?
kostja94 (a GitHub user) maintains it in kostja94/marketing-skills, which has 1,016 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 6, 2026.
Source: kostja94/marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.