functional-claude

Synchronize plugin versions across manifests, marketplace listings, and SKILL.md frontmatter.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nthplusio/functional-claude --skill functional-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: functional-claude
Source: https://github.com/nthplusio/functional-claude/tree/main/skills/functional-claude
Command: npx skills add https://github.com/nthplusio/functional-claude --skill functional-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The functional-claude skill centralizes plugin development and marketplace maintenance for the Functional Claude ecosystem, reducing misalignment between plugin manifests, marketplace entries, and skill definitions.

Core Features & Use Cases

  • Version synchronization across plugins, marketplace.json, and SKILL.md frontmatter.
  • Structured plugin skeletons and standardized skill documentation for new plugins.
  • Guided workflow for creating, updating, and publishing plugins within the repository.

Quick Start

Create a new plugin by following the repository's plugin scaffolding, then add a new skill SKILL.md under plugins/<name>/skills/<skill>/ with a valid frontmatter.

Frequently Asked Questions about functional-claude

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

FAQPage Schema
How do I sync plugin versions across marketplace manifests and SKILL.md files?

Plugin version synchronization aligns version numbers across plugin manifests, marketplace.json listings, and SKILL.md frontmatter. This process enforces consistent metadata when you add, update, or publish plugins within your repository workflow.

What is the best way to create a new plugin skeleton for the Functional Claude marketplace?

Creating a new plugin uses structured plugin skeletons and standardized skill documentation. You scaffold the plugin within the repository and add a SKILL.md file under plugins/<name>/skills/<skill>/ with valid frontmatter.

Why does my plugin metadata misalign with the marketplace listing after an update?

Metadata misalignment occurs when version numbers are manually updated in one file but not others. Enforcing version synchronization across plugin manifests, marketplace entries, and skill definitions prevents this repository workflow issue.

Can I use this workflow to update skill definitions for existing plugins?

Yes, you can update skill definitions for existing plugins. The guided workflow supports adding, updating, and aligning versions for plugins and their skills within the repository to maintain marketplace consistency.

Do I need external dependencies to manage plugin metadata synchronization?

No external dependencies are required for plugin metadata synchronization. The workflow operates entirely within the repository to align versions across manifests, marketplace listings, and SKILL.md frontmatter.

When should I not use automated version synchronization for my plugin repository?

Automated version synchronization is not suited for plugins managed outside the repository's marketplace structure. It requires standardized plugin skeletons and SKILL.md frontmatter to enforce metadata alignment correctly.