fabrcore-agent

Extend FabrCoreAgentProxy to implement lifecycle methods and integrate with Orleans grains.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FabrCore agents require a consistent pattern to connect to Orleans grains, manage lifecycle methods, handle state persistence, and coordinate timers, reminders, and health monitoring. This skill documents how to extend FabrCoreAgentProxy to implement OnInitialize, OnMessage, OnEvent, and related lifecycle hooks, while keeping concerns separated from tool integration, state, and MCPs.

Core Features & Use Cases

  • Extend FabrCoreAgentProxy to plug in business logic and lifecycle handlers (OnInitialize, OnMessage, OnEvent).
  • Manage custom per-agent state, timers, and reminders, with built-in compaction and health hooks.
  • Integrate with LLM providers, tools, plugins, and MCP services for scalable, observable agent systems.

Quick Start

Create a new FabrCore agent by extending FabrCoreAgentProxy, implement OnInitialize and OnMessage, and deploy it within an Orleans-based host.

Frequently Asked Questions about fabrcore-agent

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

FAQPage Schema
How do I build an agent with Orleans grains and lifecycle hooks?

To build an agent with Orleans grains, extend the FabrCoreAgentProxy class and implement lifecycle methods like OnInitialize and OnMessage. This pattern separates business logic from tool integration and state management, deploying the agent within an Orleans-based host.

How do I manage per-agent state, timers, and reminders in an Orleans agent framework?

Managing per-agent state, timers, and reminders involves extending the FabrCoreAgentProxy to handle custom state persistence and coordinate timers. The framework provides built-in compaction and health hooks to maintain agent state reliably across its lifecycle.

Can I integrate MCP servers and LLM tools with Orleans grains?

Yes, you can integrate MCP servers and LLM tools with Orleans grains. By extending the FabrCoreAgentProxy, developers connect LLM providers, plugins, and MCP services to build scalable, observable agent systems while keeping these concerns separated from core lifecycle logic.

What is the required structure for a FabrCore agent skill definition?

A valid FabrCore agent skill definition requires an SKILL.md file with frontmatter containing the name and description. It may also include optional scripts, references, or assets directories that are loaded automatically upon agent activation.

Why does my FabrCore agent fail to separate tool integration from state management?

FabrCore agent tool integration fails to separate from state management when developers do not extend the FabrCoreAgentProxy correctly. Implementing dedicated lifecycle hooks like OnInitialize and OnEvent ensures LLM tooling, plugins, and MCP servers remain decoupled from custom state and chat history.