Loading...
Loading...
Found 337 Skills
Generates YAML signal configs for agent simulation experiments. Use when the user wants to define what signals to track, how to extract them from run artifacts, and how to aggregate them into experiment-level metrics. Trigger when users say: "generate a signal config", "create signals for my experiment", "I want to track [metric]", "write a signal YAML", "set up extraction for [thing]", "how do I measure [behavior] across runs", "configure signals for [experiment]", "create a signal config", "create signal config file", or "build a signal config".
Extracts specific fields from YAML files efficiently using yq instead of reading entire files, saving 80-95% context. Use this skill when querying YAML files, filtering/transforming configuration data, or getting specific field(s) from large YAML files like docker-compose.yml or GitHub Actions workflows
Configure Frigate NVR with optimized YAML, object detection, recording, zones, and hardware acceleration. Use when setting up Frigate cameras, troubleshooting detection issues, configuring Coral TPU/OpenVINO, or integrating with Home Assistant.
Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML. Use when building standardized KPIs, revenue metrics, order analytics, or any reusable business metrics that need consistent definitions across teams and tools.
Create analytics question files (.question.yml) in Steedos projects. Questions are report/chart definitions stored as YAML seed data files, based on the @steedos-labs/analytics package (Metabase engine). Covers file format, dataset_query structure (MBQL), display types, visualization_settings, result_metadata, and file naming conventions.
Meta-skill for creating Claude Code skills. TRIGGERS - create skill, YAML frontmatter, validate skill, skill architecture.
Debug and troubleshoot Helm deployment failures, template errors, and configuration issues. Covers helm template, helm lint, dry-run, debugging YAML parse errors, value type errors, and resource conflicts. Use when user mentions Helm errors, debugging Helm, template rendering issues, or troubleshooting Helm deployments.
Transform structured external data (CSV/JSON) into Obsidian's linked knowledge system while preserving semantic relationships, optimizing graph structure, and preventing data corruption through systematic validation and YAML-safe template generation.Enables seamless knowledge transfer from databases, spreadsheets, and APIs into personal knowledge management, maintaining referential integrity and facilitating emergence of insights through networked thought.
Spec-driven E2E test creation: plan what to test through structured discovery phases, then scaffold a local Shiplight test project and write YAML tests by walking through the app in a browser.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
Agent-based declarative testing with YAML test specs. Tests run in sub-agents to preserve main context while executing many tests. Supports MCP servers, APIs, and browser automation. Use when: testing MCP servers, running integration tests, validating tool behavior after changes, or creating regression test suites. Keywords: yaml tests, agent testing, mcp test, integration tests.
Create new Claude Code skills with proper structure, YAML frontmatter, and best practices. Use when creating reusable knowledge modules, adding specialized guidance, or building domain-specific expertise.