medium-posts
SolidWhen the user wants to write, publish, republish, or optimize posts on Medium.com (canonical tags, distribution, Medium SEO). Also use when the user mentions "Medium," "Medium article," "Medium story," "Medium publishing," "canonical Medium," or "publish on Medium." Not for general parasite SEO when Medium is not the target platform—use parasite-seo. For AI search visibility strategy, use generative-engine-optimization.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- kostja94
- Repository
- kostja94/marketing-skills
- Created
- 3 months ago
- Last Updated
- 3 days ago
- Language
- N/A
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
parasite-seo
When the user wants to choose or execute third-party platform SEO (high-authority sites for rankings or backlinks). Also use when the user mentions "parasite SEO," "parasitic SEO," "barnacle SEO," "hosted content," "third-party publishing," "Medium SEO," "Reddit SEO," "GitHub parasite SEO," "LinkedIn Pulse SEO," "high-authority platforms," "distributed authority," "borrow domain authority," or "rank without own website." For GitHub-specific playbooks, use github. For Medium.com posts, use medium-posts. For Grokipedia, use grokipedia-recommendations. For AI answer-engine visibility (not platform selection), use generative-engine-optimization.
github
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," "repository name," "About section," "GitHub description," "GitHub topics," "GitHub Pages," "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.
content-seo
On-page / editorial SEO for written content — so what you publish ranks AND gets cited by AI answer engines. INVOKE THIS PROACTIVELY — even when the user never says "SEO" — whenever writing or editing prose meant to be published on the web — blog posts, articles, guides, tutorials, landing-page copy, product/marketing pages, press releases, "what's new"/changelog/release-note entries, FAQ pages, documentation, or Markdown content (`content/**/*.md`, `*.mdx`) and its frontmatter (title, description, slug, canonical). Covers search intent, title tags, meta descriptions, heading structure, keyword targeting, content depth, internal linking, image alt text, URL slugs, featured-snippet and AI-citation formatting, E-E-A-T, and the do's/don'ts that get content penalized. It is the editorial-SEO quality bar for all published writing produced here — reach for it on any content-writing task, not only when SEO is named. (Pairs with the technical [[seo-standards]] skill, which covers the HTML/template/redirect side.)