wfc-observe

Generate metrics collectors, alert rules, and dashboard panels from formal properties.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sam-fakhreddine/wfc --skill wfc-observe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wfc-observe
Source: https://github.com/sam-fakhreddine/wfc/tree/main/wfc/skills/wfc-observe
Command: npx skills add https://github.com/sam-fakhreddine/wfc --skill wfc-observe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of observability infrastructure by mapping formal properties (like safety, liveness, and performance) to concrete monitoring elements, thereby reducing manual configuration and ensuring comprehensive coverage.

Core Features & Use Cases

  • Property-to-Observable Mapping: Translates defined properties into actionable metrics, alerts, and dashboard configurations.
  • Automated Code Generation: Creates code for metrics collectors, alert rules, and dashboard panels.
  • Use Case: When implementing a new microservice, use this Skill to automatically generate Prometheus metrics, Grafana dashboards, and alerting rules based on the service's defined SAFETY, LIVENESS, and PERFORMANCE properties.

Quick Start

Generate observability infrastructure from the PROPERTIES.md file.

Frequently Asked Questions about wfc-observe

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

FAQPage Schema
How do I generate Prometheus metrics and Grafana dashboards from formal properties?

This approach automates observability instrumentation by mapping formal safety, liveness, and performance properties to concrete observables. It directly creates metrics collectors, alert rules, and dashboard panel configurations from your property definitions.

What is property-to-observable mapping in software observability?

Property-to-observable mapping translates formal safety, liveness, and performance characteristics into actionable monitoring elements. It converts defined properties into concrete metrics, alert rules, and dashboard panel configurations for new features.

Do I need formal property definitions to set up automated alert rules and dashboards?

Yes, formal property definitions are required to derive monitoring elements. The instrumentation generation depends on these defined safety, liveness, and performance properties to automatically create accurate metrics collectors and alert rules.

Can I automatically create metrics collectors for a new microservice from its safety properties?

Yes, you can automatically create metrics collectors for a new microservice from its safety properties. The instrumentation process maps these formal definitions directly to concrete metrics, alert rules, and dashboard panel configurations.

How do I improve monitoring coverage without manually configuring observability infrastructure?

You can improve monitoring coverage by automating observability infrastructure generation from formal properties. This reduces manual configuration by translating defined safety, liveness, and performance properties directly into metrics, alerts, and dashboards.