work-common

Load and validate work plugin configuration from the project directory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

A library of utilities for work plugins, including config loading, data normalization, and error codes.

Core Features & Use Cases

  • Load and validate work plugin config
  • Normalize data across platforms
  • Centralized error code references (future)
  • Reusable input validation helpers

Quick Start

Load configuration and extract the active work-tracker platform.

Frequently Asked Questions about work-common

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

FAQPage Schema
How do I load and validate work plugin configuration from my project?

work-common loads and validates work plugin config from your project directory, outputting JSON on stdout. It checks for config existence, extracts the active work-tracker platform, and uses standardized exit codes to signal success or validation errors for use in Bash scripts.

Can I use work-common to auto-detect my work-tracker platform across GitHub and related platforms?

Yes. work-common enables auto-detection by loading project-level configuration and identifying the active work-tracker platform, designed for direct Bash invocation by helper scripts like config-loader.sh and get-repo-info.sh.

What's the best way to normalize work data across multiple platforms?

work-common provides data normalization utilities as a shared library for work plugins, ensuring consistent handling of project configuration and platform-specific data across GitHub and related services.

Do I need bash and jq to use work-common?

Yes. work-common requires bash and jq as dependencies. It's designed for direct Bash invocation and outputs JSON, which jq can parse and manipulate.

How do I integrate work-common with my existing work plugin scripts?

Invoke work-common directly from Bash to load config and validate inputs; it outputs JSON and uses exit codes to communicate success or errors, making it suitable for chaining with other helper scripts in your work-tracker workflow.