This skill fetches up-to-date documentation and code examples from libraries using the Context7 API.

Contextual Retrieval implementation for RAG - chunks clinical notes with LLM-generated context prepended to each chunk before embedding. Improves citation accuracy by 49% per Anthropic research.

Review pull requests for code quality, security vulnerabilities, best practices, and potential issues. Use when reviewing PRs, examining diffs, or providing code review feedback.

Master Continental philosophy and Critical Theory. Use for: post-structuralism, deconstruction, Frankfurt School, hermeneutics, psychoanalysis. Triggers: 'Foucault', 'power/knowledge', 'deconstruction', 'Derrida', 'différance', 'critical theory', 'Frankfurt School', 'Adorno', 'Habermas', 'genealogy', 'discourse', 'Lacan', 'Deleuze', 'rhizome', 'biopolitics', 'ideology', 'alienation', 'reification', 'hermeneutics', 'Gadamer', 'post-structuralism', 'logocentrism'.

Expert in Continental tradition from Kant through phenomenology, existentialism, structuralism, and post-structuralism

Continuation format reference for GSD sessions

Respond to CEU or professional credit inquiries. Use when a learner asks whether a course qualifies for continuing education credits.

Validate scene content against all prior episodes and established canon to detect continuity violations, invented details, and timeline errors.

Create or update continuity ledger for state preservation across clears

Apply Google's continuous fuzzing methodology using OSS-Fuzz and ClusterFuzz. Emphasizes coverage-guided fuzzing, automated bug triage, and integration into CI/CD. Use when building robust testing infrastructure or finding security vulnerabilities at scale.

After completing a task, briefly reflect and capture learnings.

Convert repeated tasks into skills, version control them in Git, and polish iteratively based on usage feedback to achieve 20% consistency gain.

Contract review and legal analysis

Review contracts to identify key terms, risks, obligations, and negotiation opportunities

Generate legal contracts from templates with variable substitution and clause management

Author OpenAPI/AsyncAPI specs, contracts, and mocks.

Design and manage API contracts before implementation using OpenAPI and AsyncAPI specifications for contract-first development

Use when asked to generate legal contracts, agreements, or documents from templates with variable substitution and formatting.

You are an expert in procurement contract management and negotiation. Your goal is to help organizations manage supplier contracts throughout their lifecycle, negotiate favorable terms, ensure complia

Common Solidity design patterns and implementations for secure smart contract development. Use when implementing standard functionality like access control, upgradeability, or token standards.

Analyze commercial agreements against organizational standards with clause-by-clause review

Analyzes freelance contracts and Statements of Work (SOW) to identify potential risks, scope creep, and unfavorable terms, providing plain-language explanations.

Test and validate API contracts against specifications

Ensure API contracts don't break consumers.

Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing. Use when testing API contracts or coordinating distributed teams.

AI-powered contractor matching and selection for construction projects. Analyze contractor capabilities, past performance, certifications, and project requirements to recommend optimal matches.

Эксперт CONTRIBUTING.md. Используй для open source guidelines, PR процессов и contributor onboarding.

Contribution readiness assessment analyzing project guidelines and requirements

>

Generate detailed control implementation guidance, technical steps, and implementation plans for OSCAL security controls. Use this skill to create implementation narratives, technical procedures, and deployment plans.

Extract and analyze agent reasoning loops, step functions, and termination conditions. Use when needing to (1) understand how an agent framework implements reasoning (ReAct, Plan-and-Solve, Reflection, etc.), (2) locate the core decision-making logic, (3) analyze loop mechanics and termination conditions, (4) document the step-by-step execution flow of an agent, or (5) compare reasoning patterns across frameworks.

Create and analyze OSCAL Control Mapping documents to establish formal relationships between controls across different frameworks (NIST 800-53, ISO 27001, CIS, PCI-DSS, etc.). Use this skill to document control equivalencies, gaps, and harmonization for multi-framework compliance.

Maps NIST controls to FedRAMP requirements and documents. Use when helping with control implementation, compliance mapping, security baseline alignment, or understanding control requirements.

Creates a control panel that allows runtime modification of values. When Claude needs to expose controls for the user to adjust variables and values.

Control active sessions by terminating problematic sessions, managing runaway queries, and handling blocking situations

Provides a systematic checklist for optimizing control structures (loops, conditionals, control flow) to create self-documenting, maintainable code. Use this skill when writing new control logic, refactoring existing code, or conducting code reviews to minimize complexity and improve readability.

Execute implementation work in a strictly controlled manner.

Use when symfony controller cleanup

controller-expert

Control Spotify playback and manage playlists via MCP server. Use when user requests playing music, controlling Spotify, creating playlists, searching songs, or managing their Spotify library.

Extract and analyze security controls from OSCAL catalogs, profiles, and SSPs. Use this skill to get detailed information about control hierarchies, statements, parameters, and implementation status for compliance analysis.

Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages.

When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.

Conventional Commits specification format. Use when creating commit messages. Format: <type>(<scope>): <description>. Types: feat, fix, chore, docs, test, refactor, style, perf. CRITICAL: All commits must follow conventional commit format.

>

Automatically apply standard coding conventions when writing or modifying code. Use this skill when working with Python, TypeScript, JavaScript, Go, PHP, or creating git commits. Triggers include writing new code, refactoring existing code, or committing changes in supported languages.

Technical conversation log with factual accuracy and precision tailored specifically for DEVELOPER and ENGINEER profiles. Provides systematic guidance for capturing decisions, outcomes, and next steps. Use when user asks to create technical conversation logs for reviews, architecture discussions, or implementation sessions.

This skill should be used when users need to save, search, or retrieve Claude Code conversation transcripts. Use this skill when users ask to save the current conversation, search through past conversations for context, or retrieve information from previous sessions. Also use when appropriate to proactively save important conversations at natural breakpoints (e.g., after completing a major feature, fixing a critical bug, or when the user indicates they're done with a session).