core

Centralize FABER configuration loading, state management, and status-card generation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, and includes scripts (resource) components.

What problem does it solve?

Central utilities that underpin all FABER workflows, including configuration loading, state management, and status reporting. This skill provides the foundational operations that other FABER agents rely on to track progress, persist state, and communicate status.

Core Features & Use Cases

  • Load and parse FABER configuration
  • Manage workflow state (read, update, write)
  • Generate and post status cards to work tracking systems
  • Handle template variable substitution

Quick Start

Use the core utilities to load config and read the current FABER state before kicking off a workflow.

Frequently Asked Questions about core

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

FAQPage Schema
How do I centralize configuration and state management across my FABER workflow phases?

FABER's core utilities automate config loading, state reads/updates/writes, and template substitutions across frame, architect, build, evaluate, and release phases. Load configuration once, then manage workflow state centrally to ensure idempotent operations and consistent state across all phases.

Can I use bash and jq to automate workflow state tracking and status reporting?

Yes. The core Skill provides bash and jq utilities to read current state, update it idempotently, and generate status cards for posting to work-tracking systems. This enables CLI-based agent integration with robust error handling and environment-agnostic templates.

What's the best way to handle template variable substitution in automated workflows?

Core utilities perform template variable substitution as part of config parsing and status-card generation. Define templates once and reuse them across workflow phases; substitution is handled automatically during config load and state updates.

How do I ensure stateless execution and idempotent state updates in my workflow?

The core Skill meets requirements for stateless execution and idempotent state updates by centralizing state management logic. Each state write is idempotent, allowing safe re-execution without side effects or duplicate state changes.

Does this Skill work with pluggable backends for state storage?

Yes. Core utilities support pluggable backends for state persistence, enabling flexibility in where state is stored while maintaining a consistent interface across FABER phases and agent integrations.

What dependencies do I need before using core FABER workflow utilities?

You need bash and jq installed. These are the foundational dependencies for config parsing, state management operations, and status-card generation across all FABER workflow phases.