SEO keyword clustering with topic organization, content hub architecture, internal linking strategies. Use for content strategy, keyword research, pillar page structures, or encountering cluster organization, hub architecture, internal linking errors.
Write clear, unambiguous system requirements using the EARS (Easy Approach to Requirements Syntax) methodology. Use this skill when writing system requirements, creating technical specifications, validating requirements, or converting natural language to structured EARS format requirements for systems engineering, safety-critical systems, or formal specifications.
Format and validate Obsidian wiki links with proper filename, section, and folder conventions. Verify links exist before creation and fix broken links. Use when creating or checking wiki links in markdown files.
Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.
USE WHEN: user asks "explain", "teach me", "how does X work", "help me understand", or wants to learn concepts from first principles with interactive comprehension checks. DO NOT USE WHEN: user wants quick answers, code implementation, or already understands the concept and just needs a reminder.
USE WHEN: user asks to create a skill, scaffold a new capability, codify expertise into reusable instructions, or says "create skill", "new skill", "make a skill". DO NOT USE WHEN: user wants to use existing skills, needs general help, or is asking about skill concepts rather than creating one.
Skill Creator - Meta-skill for creating new domain-specific skills. Automatically activates when creating skills about specific topics or expertise areas.
When any part of the application needs to be found or understood.
Evaluates agent skills against Anthropic's best practices. Use when asked to review, evaluate, assess, or audit a skill for quality. Analyzes SKILL.md structure, naming conventions, description quality, content organization, and identifies anti-patterns. Produces actionable improvement recommendations.
Use for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
This skill should be used after productive sessions to extract learnings and route them to appropriate Reusable Intelligence Infrastructure (RII) components. Use when corrections were made, format drift was fixed, new patterns emerged, or the user explicitly asks to "harvest learnings" or "capture session intelligence". Transforms one-time fixes into permanent organizational knowledge by implementing updates across multiple files.
Brief description of what this skill does. Should be clear enough that Claude knows when to invoke it. Max 1024 characters.
Sistematik debugging döngüsü - reproduce, isolate, hypothesize, fix.
Hacker News API via curl. Use this skill to fetch top stories, new posts, comments, and user profiles from Hacker News.
Convert Obsidian WikiLinks ([[...]]) to standard Markdown links ([...](...)) for GitHub compatibility. This skill should be used when users need to make README files or other Markdown documents GitHub-compatible while maintaining Obsidian functionality, or when batch converting WikiLinks across multiple files.
Customer interview question bank and synthesis templates for product discovery.
Create Architecture Decision Records (ADRs) to document significant technical decisions, their context, alternatives considered, and consequences. Use when making architectural choices, selecting libraries/frameworks, or designing system components.
Transform vague or ambiguous requirements into precise, actionable specifications through structured questioning. Use when user says "clarify", "refine requirements", or when requirements are unclear, incomplete, or open to multiple interpretations. Always use before implementing any ambiguous feature request.
Query fan-out coverage for AI visibility. Covers semantic variation analysis and sub-question targeting.
Transform reading notes and insights into polished, authentic content (blogs, social media, visualizations) that preserves your unique voice and avoids AI-style writing. Creates content that sounds unmistakably human.
Find where potential customers discuss problems online and extract their language patterns. Provides starting points for community research, not exhaustive coverage.
Build entity triplets and brand associations that LLMs recognize and cite consistently.
