log-validator
Validates logs against type-specific schemas checking frontmatter, structure, and required fields
Discover Research skills, compare source repositories and read the instructions for each workflow.
Validates logs against type-specific schemas checking frontmatter, structure, and required fields
Post comments to issues via Fractary CLI with optional FABER context tracking
Create relationships between issues via comment references
Executes FABER plans by spawning faber-manager agents. Simple and reliable.
Sync all projects in an organization with codex repository (with parallel execution). Delegates to fractary CLI for organization-wide sync operations.
Create and manage Git branches with safety checks and validation
Discover repositories in an organization for sync operations
Execute FABER phase hooks (pre/post phase boundaries)
Create semantic commits with FABER metadata and conventional commit format
Generates concise summaries of log content using type-specific summarization templates
List comments on issues with optional filtering via Fractary CLI
Search and list issues via Fractary CLI
GitHub-specific sync mechanism - file copying, pattern matching, and safety checks
Creates or updates logs using type-specific templates with automatic validation and formatting
[DEPRECATED] GitHub Issues handler - Use Fractary CLI instead
Initialize spec plugin configuration
Analyzes Claude Code project structure detecting architectural patterns and anti-patterns by executing detection scripts
Analyze infrastructure deployment errors - categorize error types (permission/ config/resource/state), search issue log for historical solutions, rank solutions by success rate and context match, propose automa...
Common utilities for work plugin operations
Deploy database migrations safely across environments
Migrates codex configuration files from v2.0 push-based sync to v3.0 pull-based retrieval format with automatic backups
Handles FABER workflow feedback requests - posting to issues and tracking responses
Extracts patterns, errors, and insights from operational logs using type-specific analysis templates
Generate semantic branch names from work item metadata following conventions
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.