.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/l3digitalnet/claude-code-plugins
home/skills/l3digitalnet/claude-code-plugins
l3digitalnet avatar

l3digitalnet/claude-code-plugins

38 skills

View on GitHub
$npx skills add l3digitalnet/claude-code-plugins
SkillInstalls
agent-handoffUse when starting or closing an agent session, routing durable repository facts, maintaining status or task state, recording bugs, validating handoff…—allUpdate all three documentation layers (repo, wiki, Notion) via parallel sub-agent propagation, then run drift audit.—authorAuthor the canonical project spec and decompose it into phases for execution by /spec-pipeline:execute-phase. Run once at project inception.—driftRead-only documentation drift audit across infrastructure, wiki, and Notion by dispatching the up-docs-audit-drift sub-agent; reports findings, never fixes.—execute-phaseExecute the next pending phase of the named project end-to-end — derive the phase spec from the master, plan it, implement under TDD with review gates, and…—ha-architectureHome Assistant core internals — event bus, state machine, service registry, and integration loading.—ha-async-patternsWrite correct async Python code for Home Assistant integrations.—ha-blueprintsHome Assistant YAML blueprints — reusable automation templates with configurable inputs.—ha-config-flowHome Assistant config flow for initial integration setup. Use when creating or debugging config_flow.py, the user-facing setup wizard, unique_id handling, or…—ha-config-migrationConfig entry version migration in Home Assistant. Use when incrementing VERSION or MINOR_VERSION, implementing async_migrate_entry, or migrating stored entry…—ha-coordinatorImplement or fix a Home Assistant DataUpdateCoordinator for centralized data fetching.—ha-debuggingDebug and troubleshoot Home Assistant integration issues. Use when mentioning error, debug, not working, unavailable, traceback, exception, logs, failing,…—ha-deprecation-fixesFix Home Assistant deprecation warnings and upgrade integrations to newer HA versions.—ha-device-conditions-actionsDevice conditions and actions for Home Assistant automation. Use when implementing device_condition.py, device_action.py, condition state checks, or…—ha-device-triggersDevice triggers for Home Assistant automation. Use when implementing device_trigger.py, allowing automations to fire on hardware events like button presses or…—ha-diagnosticsImplement diagnostics for a Home Assistant integration. Required for Gold tier on the Integration Quality Scale.—ha-documentationGenerate documentation for Home Assistant integrations. Creates README.md, Home Assistant docs pages, and HACS info pages.—ha-entity-lifecycleEntity lifecycle and device/entity registries in Home Assistant.—ha-entity-platformsCreate Home Assistant entity platforms (sensor, binary_sensor, switch, light, cover, climate, button, number, select, etc.).—ha-hacsHACS metadata requirements for a Home Assistant integration — hacs.json, manifest.json fields, and repository structure.—ha-hacs-publishingPublish a Home Assistant integration to HACS — GitHub Actions validation, release workflow, brand submission, and adding to the HACS default repository.—ha-integration-scaffoldScaffold a new Home Assistant integration with correct file structure, manifest, and boilerplate.—ha-migrationHome Assistant integration upgrade guide — config entry version migration and deprecation fixes.—ha-options-flowHome Assistant options flow for post-setup user preferences. Use when adding or fixing an options flow, allowing users to change integration settings after…—ha-quality-reviewReview a Home Assistant integration against the Integration Quality Scale (IQS). Covers all 52 official rules across Bronze, Silver, Gold, and Platinum tiers.—ha-recorderWork with the Home Assistant recorder and statistics. Use when asked about history, statistics, long-term stats, database, recorder exclusion, or historical…—ha-repairsImplement repair issues for Home Assistant integrations. Gold tier IQS requirement.—ha-scriptsHome Assistant YAML scripts — callable, reusable action sequences with optional parameters.—ha-service-actionsGenerate and explain Home Assistant service actions for controlling entities (lights, switches, climate, media, covers) in Python and YAML.—ha-testingWrite tests for Home Assistant integrations using pytest and the hass fixture.—ha-websocket-apiImplement WebSocket API commands for Home Assistant integrations.—ha-yaml-automationsHome Assistant YAML automations — triggers, conditions, and actions.—notionUpdate Notion pages with strategic and organizational context from the current session by dispatching the up-docs-propagate-notion sub-agent.—refresh-plugin-cacheThis skill should be used when the user asks to "refresh the plugin cache", "update plugin cache", "sync plugin cache", "update installed plugins", "check for…—repoUpdate repository documentation (README.md, docs/, CLAUDE.md) based on session changes by dispatching the up-docs-propagate-repo sub-agent.—test-plugin1. Ask user which plugin to test (do NOT assume from previous session) 2. Clear any existing test data for other plugins 3.—uv-strict-pythonConfigures Python projects to the Python Tooling SSOT Standard (uv, Ruff, BasedPyright strict, pytest+coverage, pip-audit).—wikiUpdate the llm-wiki knowledge base (remote LXC CT 103, /srv/workspaces/llm-wiki, over SSH) with implementation-level details from the current session by…—