fabrcore-plugins-tools

Create and register FabrCore plugins and standalone tools with standardized metadata and DI integration.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/vulcan365/FabrCore --skill fabrcore-plugins-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabrcore-plugins-tools
Source: https://github.com/vulcan365/FabrCore/tree/main/docs/skills/fabrcore-plugins-tools
Command: npx skills add https://github.com/vulcan365/FabrCore --skill fabrcore-plugins-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FabrCore plugin and tool ecosystems are complex to implement and maintain. This Skill provides standardized patterns and metadata scaffolding to create, register, and manage Plugins and Standalone Tools with consistent discovery, configuration, and lifecycle semantics.

Core Features & Use Cases

  • Templates and patterns for Stateful Plugins via IFabrCorePlugin with PluginAlias and Description attributes
  • Clear lifecycle guidance: discovery, resolution, initialization, tool extraction, disposal, with DI and settings
  • Stand-alone tool support with ToolAlias, Description, and note-based metadata for pure functions and cross-agent workflows

Quick Start

Create a SKILL.md in a new skill folder with proper frontmatter name and description and optionally add scripts/, references/, or assets/ to extend functionality.

Frequently Asked Questions about fabrcore-plugins-tools

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

FAQPage Schema
How do I create FabrCore plugins with standardized metadata and discovery?

To create FabrCore plugins, you use standardized templates with IFabrCorePlugin, PluginAlias, and Description attributes to enforce frontmatter metadata, enabling consistent tool discovery and dependency injection integration across Orleans deployments.

What is the lifecycle of a stateful FabrCore plugin?

The FabrCore plugin lifecycle progresses through discovery, resolution, initialization, tool extraction, and disposal, managed with DI and settings to maintain state and enforce safety checks throughout the plugin's execution context.

Can I build standalone tools for inter-agent workflows without a full plugin lifecycle?

Yes, you can build standalone tools using ToolAlias, Description, and note-based metadata to scaffold pure functions for cross-agent workflows, bypassing the full stateful plugin lifecycle while maintaining tool discovery.

Does this Skill work with Orleans-based FabrCore deployments for tool catalogs?

Yes, this Skill facilitates building tool catalogs and plugin ecosystems across Orleans-based FabrCore deployments by providing standardized metadata scaffolding and dependency injection integration for inter-agent toolchains.

What directory structure do I need to extend FabrCore tool functionality?

You extend FabrCore tool functionality by creating a SKILL.md with proper frontmatter name and description in a new skill folder, then optionally adding scripts, references, or assets directories for additional components.

Why enforce frontmatter name and description when building FabrCore tools?

Enforcing frontmatter name and description standardizes tool metadata for reliable discovery and resolution, ensuring safety checks and consistent lifecycle semantics across complex FabrCore plugin ecosystems.