content-gap-analysis
About
This skill analyzes competitor content to identify keywords and topics they cover that you don't, revealing strategic gaps in your content strategy. It's used for content planning, finding quick-win opportunities, and understanding competitive performance. Key capabilities include keyword gap analysis, topic coverage mapping, and identifying missing content formats.
Quick Install
Claude Code
Recommendednpx skills add NeverSight/skills_feed -a claude-code/plugin add https://github.com/NeverSight/skills_feedgit clone https://github.com/NeverSight/skills_feed.git ~/.claude/skills/content-gap-analysisCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
release-standards
DocumentsThis skill provides semantic versioning (semver) guidelines and changelog formatting standards for software releases. Use it when preparing releases to correctly increment version numbers (major/minor/patch) and structure changelog entries. It includes rules for pre-release identifiers and clear examples for developers.
commit-standards
DocumentsThis skill formats Git commit messages according to the Conventional Commits standard. It provides templates and type definitions (like `feat`, `fix`, `refactor`) to ensure consistency when writing or reviewing commits. Use it during the commit process to create clear, structured commit history.
huggingface-tokenizers
DocumentsThis skill provides high-performance tokenization using HuggingFace's Rust-based library, processing 1GB of text in under 20 seconds. It supports BPE, WordPiece, and Unigram algorithms while enabling custom tokenizer training and alignment tracking. Use it when you need production-fast tokenization or to build custom tokenizers integrated with the transformers ecosystem.
nano-pdf
Documentsnano-pdf is a CLI tool that lets developers edit PDFs using natural-language instructions, like changing text or fixing typos on specific pages. It's ideal for quick, programmatic PDF modifications directly from the terminal. Always verify the output, as page numbering can vary between versions.