keyword-extractor
Extracts up to 50 highly relevant SEO keywords from text. Use when user wants to generate or extract keywords for given text.
What this skill does
# Keyword Extractor Extracts **max 50 relevant keywords** from text and formats them in a strict machine-ready structure. --- ## QUICK START Jump to any section: 1. [CORE MANDATE](#core-mandate) – Output rules and formatting 2. [WHEN TO USE](#when-to-use) – Trigger conditions for this skill 3. [KEYWORD QUALITY RULES](#keyword-quality-rules) – Priorities and forbidden keywords 4. [WORKFLOW](#workflow) – Step-by-step generation and processing 5. [FAILURE HANDLING](#failure-handling) – Short text or edge cases --- # CORE MANDATE Return **exactly one comma-separated line** of keywords, following these rules: - max 50 keywords - ordered by relevance - all lowercase - no duplicates or near-duplicates - mix of single words and 2–4 word phrases - no numbering, bullets, explanations, or trailing period --- ## When to Use Use this skill when the user wants to generate or extract **SEO-friendly keywords or tags** from text including: - Extracting keywords or tags for any given text or paragraph - Creating **comma-separated keywords or tags** suitable for SEO, search, or metadata - Generating topic-specific keywords or tags based on the content’s main subjects and concepts This skill should be triggered for **all text-based keyword extraction requests**, regardless of phrasing, as long as the goal is SEO, tagging, or metadata generation. Do NOT trigger this skill for: - Summaries or paraphrasing requests - Text analysis without keyword generation --- # KEYWORD QUALITY RULES Prefer noun phrases over verbs or adjectives. Prefer keywords useful for: - SEO and search - tagging - metadata Prioritize: - domain terminology - meaningful nouns - search phrases - entities - technical concepts Avoid weak keywords like: - things and various topics - general concepts - important ideas - methods **IMPORTANT: Each keyword must strictly represent a phrase that a user would type into a search engine** --- # WORKFLOW ## Step 1 — Analyze Identify: - main subject - key topics - domain terminology - entities - concepts Ignore filler words. --- ## Step 2 — Generate Keywords Generate up to 50 strictly SEO-friendly keywords directly from the text. Include: - core topics - domain terminology - related concepts - common search queries Allowed formats: - single words - 2 word phrases - 3 word phrases - 4 word phrases Example: ```machine learning, neural networks, deep learning models, ai algorithms, data science tools``` Avoid vague keywords, filler phrases, adjectives without nouns like: ```important methods, different ideas, various techniques, things``` Keywords must not exceed 4 words. --- ## Step 3 — Rank Order keywords by SEO importance using these signals: 1. main topic of the text 2. high-value domain terminology 3. technologies, tools, or entities mentioned 4. common search queries related to the topic 5. supporting contextual topics Most important keywords should always appear first. --- ## Step 4 — Normalize Ensure: - lowercase, comma separated, no duplicates - ≤50 keywords - Remove near-duplicate keywords that represent the same concept. - Keep only the most common search phrase. - If two keywords represent the same concept, keep only the more common search phrase. --- ## Step 5 — Validate Before returning output ensure: - keyword_count <= 50 - no duplicates and near-duplicates - all lowercase and comma separated - no trailing period - each keyword is a clear searchable topic - keywords do not exceed 4 words If any rule fails regenerate the list. --- # FAILURE HANDLING If text is very short, infer likely topics and still generate keywords. Never exceed 50 keywords. --- ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".