skills.rest
ImproperSubset
ImproperSubsetCOMMUNITY
Explore all skills by this author →
GitHub

cc-plugin-extensions

Create project-specific plugin extension files with YAML frontmatter.

1|Updated Jan 4, 2026
Search Tags:#workflow#codebase#plugin#project-context#local.md#extend
One-click install
npx skills add https://github.com/ImproperSubset/hh-agentics --skill cc-plugin-extensions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-plugin-extensions
Source: https://github.com/ImproperSubset/hh-agentics/tree/main/cc-governance/skills/cc-plugin-extensions
Command: npx skills add https://github.com/ImproperSubset/hh-agentics --skill cc-plugin-extensions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you tailor marketplace plugin behavior to a specific codebase by creating and using project-context extensions (.local.md) that bridge general plugin guidance with project-specific conventions, paths, and workflows.

Core Features & Use Cases

  • Create and manage .local.md extension files that attach plugin context to a project
  • Document plugin usage patterns, file paths, and project conventions for a given codebase
  • Enable targeted plugin customization during installation, extension, or onboarding tasks

Quick Start

To enable project-specific plugin context, place a file like .claude/cc-governance-skills.local.md in your repository and fill in the required frontmatter for plugin and project, then reference the plugin usage in your workflow.

Frequently Asked Questions about cc-plugin-extensions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize a plugin for a specific codebase?▼

To customize a plugin for a specific codebase, you create project-specific extension files like .local.md that document file paths, conventions, and workflows bridging general plugin guidance to your repository.

What is a .local.md extension file used for?▼

A .local.md extension file attaches project-specific context to a plugin by documenting local file paths, conventions, and processes, bridging general plugin guidance to a specific codebase during install or customize workflows.

How do I add project context to a plugin workflow?▼

Add project context to a plugin workflow by placing a .local.md file in the .claude directory with required YAML frontmatter for name and description, defining plugin and project metadata for your codebase.

What frontmatter is required for plugin extension files?▼

Plugin extension files require YAML frontmatter with name and description fields. This metadata ties the .local.md file to the specific plugin and project, enabling targeted codebase customization.

Can I document plugin conventions for onboarding a new codebase?▼

Yes, you can document plugin conventions for onboarding by creating .local.md extension files that map general plugin guidance to project-specific paths and processes during installation or onboarding tasks.

Where should project-specific plugin metadata files be stored?▼

Project-specific plugin metadata files should be stored under the .claude directory in your repository, such as .claude/cc-governance-skills.local.md, enabling plugins to reference local context during workflows.

Related Skills

Explore More Software Engineering Skills→
VivekSinghRathore7VivekSinghRathore7

plugin-settings

Manage Claude Code plugin settings via YAML frontmatter and markdown files.

Community
Intermediate
EpiphyticEpiphytic
7

cowork-plugin-customizer

Customize Claude Code plugins for organization-specific tools and workflows.

Official
Advanced
NagyViktNagyVikt
2

plugin-creator

Scaffold Codex plugin directories and update marketplace.json manifests.

Community
Intermediate
fcakyonfcakyon
1.0k

plugin-settings

Store per-project plugin configuration in .claude/*.local.md files with YAML frontmatter.

Community
Intermediate