@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/observability-monitoring-monitor-setup.md

@@ -0,0 +1,48 @@
+---
+name: observability-monitoring-monitor-setup
+description: "You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da"
+---
+
+# Monitoring and Observability Setup
+
+You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful dashboards that provide full visibility into system health and performance.
+
+## Use this skill when
+
+- Working on monitoring and observability setup tasks or workflows
+- Needing guidance, best practices, or checklists for monitoring and observability setup
+
+## Do not use this skill when
+
+- The task is unrelated to monitoring and observability setup
+- You need a different domain or tool outside this scope
+
+## Context
+The user needs to implement or improve monitoring and observability. Focus on the three pillars of observability (metrics, logs, traces), setting up monitoring infrastructure, creating actionable dashboards, and establishing effective alerting strategies.
+
+## Requirements
+$ARGUMENTS
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Output Format
+
+1. **Infrastructure Assessment**: Current monitoring capabilities analysis
+2. **Monitoring Architecture**: Complete monitoring stack design
+3. **Implementation Plan**: Step-by-step deployment guide
+4. **Metric Definitions**: Comprehensive metrics catalog
+5. **Dashboard Templates**: Ready-to-use Grafana dashboards
+6. **Alert Runbooks**: Detailed alert response procedures
+7. **SLO Definitions**: Service level objectives and error budgets
+8. **Integration Guide**: Service instrumentation instructions
+
+Focus on creating a monitoring system that provides actionable insights, reduces MTTR, and enables proactive issue detection.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.

package/merged-commands/observability-monitoring-slo-implement.md

@@ -0,0 +1,43 @@
+---
+name: observability-monitoring-slo-implement
+description: "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that balances reliability with delivery velocity."
+---
+
+# SLO Implementation Guide
+
+You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based engineering practices. Design comprehensive SLO frameworks, establish meaningful SLIs, and create monitoring systems that balance reliability with feature velocity.
+
+## Use this skill when
+
+- Defining SLIs/SLOs and error budgets for services
+- Building SLO dashboards, alerts, or reporting workflows
+- Aligning reliability targets with business priorities
+- Standardizing reliability practices across teams
+
+## Do not use this skill when
+
+- You only need basic monitoring without reliability targets
+- There is no access to service telemetry or metrics
+- The task is unrelated to service reliability
+
+## Context
+The user needs to implement SLOs to establish reliability targets, measure service performance, and make data-driven decisions about reliability vs. feature development. Focus on practical SLO implementation that aligns with business objectives.
+
+## Requirements
+$ARGUMENTS
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Safety
+
+- Avoid setting SLOs without stakeholder alignment and data validation.
+- Do not alert on metrics that include sensitive or personal data.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.

package/merged-commands/observe-whatsapp.md

@@ -0,0 +1,109 @@
+---
+name: observe-whatsapp
+description: "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message failures, or webhook delivery problems."
+source: "https://github.com/gokapso/agent-skills/tree/master/skills/observe-whatsapp"
+risk: safe
+---
+
+# Observe WhatsApp
+
+## When to use
+
+Use this skill for operational diagnostics: message delivery investigation, webhook delivery debugging, error triage, and WhatsApp health checks.
+
+## Setup
+
+Env vars:
+- `KAPSO_API_BASE_URL` (host only, no `/platform/v1`)
+- `KAPSO_API_KEY`
+
+## How to
+
+### Investigate message delivery
+
+1. List messages: `node scripts/messages.js --phone-number-id <id>`
+2. Inspect message: `node scripts/message-details.js --message-id <id>`
+3. Find conversation: `node scripts/lookup-conversation.js --phone-number <e164>`
+
+### Triage errors
+
+1. Message errors: `node scripts/errors.js`
+2. API logs: `node scripts/api-logs.js`
+3. Webhook deliveries: `node scripts/webhook-deliveries.js`
+
+### Run health checks
+
+1. Project overview: `node scripts/overview.js`
+2. Phone number health: `node scripts/whatsapp-health.js --phone-number-id <id>`
+
+## Scripts
+
+### Messages
+
+| Script | Purpose |
+|--------|---------|
+| `messages.js` | List messages |
+| `message-details.js` | Get message details |
+| `lookup-conversation.js` | Find conversation by phone or ID |
+
+### Errors and logs
+
+| Script | Purpose |
+|--------|---------|
+| `errors.js` | List message errors |
+| `api-logs.js` | List external API logs |
+| `webhook-deliveries.js` | List webhook delivery attempts |
+
+### Health
+
+| Script | Purpose |
+|--------|---------|
+| `overview.js` | Project overview |
+| `whatsapp-health.js` | Phone number health check |
+
+### OpenAPI
+
+| Script | Purpose |
+|--------|---------|
+| `openapi-explore.mjs` | Explore OpenAPI (search/op/schema/where) |
+
+Install deps (once):
+```bash
+npm i
+```
+
+Examples:
+```bash
+node scripts/openapi-explore.mjs --spec platform search "webhook deliveries"
+node scripts/openapi-explore.mjs --spec platform op listWebhookDeliveries
+node scripts/openapi-explore.mjs --spec platform schema WebhookDelivery
+```
+
+## Notes
+
+- For webhook setup (create/update/delete, signature verification, event types), use `integrate-whatsapp`.
+
+## References
+
+- [references/message-debugging-reference.md](references/message-debugging-reference.md) - Message debugging guide
+- [references/triage-reference.md](references/triage-reference.md) - Error triage guide
+- [references/health-reference.md](references/health-reference.md) - Health check guide
+
+## Related skills
+
+- `integrate-whatsapp` - Onboarding, webhooks, messaging, templates, flows
+- `automate-whatsapp` - Workflows, agents, and automations
+
+<!-- FILEMAP:BEGIN -->
+```text
+[observe-whatsapp file map]|root: .
+|.:{package.json,SKILL.md}
+|assets:{health-example.json,message-debugging-example.json,triage-example.json}
+|references:{health-reference.md,message-debugging-reference.md,triage-reference.md}
+|scripts:{api-logs.js,errors.js,lookup-conversation.js,message-details.js,messages.js,openapi-explore.mjs,overview.js,webhook-deliveries.js,whatsapp-health.js}
+|scripts/lib/messages:{args.js,kapso-api.js}
+|scripts/lib/status:{args.js,kapso-api.js}
+|scripts/lib/triage:{args.js,kapso-api.js}
+```
+<!-- FILEMAP:END -->
+

package/merged-commands/obsidian-clipper-template-creator.md

@@ -0,0 +1,64 @@
+---
+name: obsidian-clipper-template-creator
+description: Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
+---
+
+# Obsidian Web Clipper Template Creator
+
+This skill helps you create importable JSON templates for the Obsidian Web Clipper.
+
+## Workflow
+
+1. **Identify User Intent:** specific site (YouTube), specific type (Recipe), or general clipping?
+2. **Check Existing Bases:** The user likely has a "Base" schema defined in `Templates/Bases/`.
+    - **Action:** Read `Templates/Bases/*.base` to find a matching category (e.g., `Recipes.base`).
+    - **Action:** Use the properties defined in the Base to structure the Clipper template properties.
+    - See [references/bases-workflow.md](references/bases-workflow.md) for details.
+3. **Fetch & Analyze Reference URL:** Validate variables against a real page.
+    - **Action:** Ask the user for a sample URL of the content they want to clip (if not provided).
+    - **Action (REQUIRED):** Use `WebFetch` or a browser DOM snapshot to retrieve page content before choosing any selector.
+    - **Action:** Analyze the HTML for Schema.org JSON, Meta tags, and CSS selectors.
+    - **Action (REQUIRED):** Verify each selector against the fetched content. Do not guess selectors.
+    - See [references/analysis-workflow.md](references/analysis-workflow.md) for analysis techniques.
+4. **Draft the JSON:** Create a valid JSON object following the schema.
+    - See [references/json-schema.md](references/json-schema.md).
+5. **Verify Variables:** Ensure the chosen variables (Preset, Schema, Selector) exist in your analysis.
+    - **Action (REQUIRED):** If a selector cannot be verified from the fetched content, state that explicitly and ask for another URL.
+    - See [references/variables.md](references/variables.md).
+
+## Selector Verification Rules
+
+- **Always verify selectors** against live page content before responding.
+- **Never guess selectors.** If the DOM cannot be accessed or the element is missing, ask for another URL or a screenshot.
+- **Prefer stable selectors** (data attributes, semantic roles, unique IDs) over fragile class chains.
+- **Document the target element** in your reasoning (e.g., "About sidebar paragraph") to reduce mismatch.
+
+## Output Format
+
+**ALWAYS** output the final result as a JSON code block that the user can copy and import.
+
+```json
+{
+  "schemaVersion": "0.1.0",
+  "name": "My Template",
+  ...
+}
+```
+
+## Resources
+
+- [references/variables.md](references/variables.md) - Available data variables.
+- [references/filters.md](references/filters.md) - Formatting filters.
+- [references/json-schema.md](references/json-schema.md) - JSON structure documentation.
+- [references/bases-workflow.md](references/bases-workflow.md) - How to map Bases to Templates.
+- [references/analysis-workflow.md](references/analysis-workflow.md) - How to validate page data.
+
+### Official Documentation
+
+- [Variables](https://help.obsidian.md/web-clipper/variables)
+- [Filters](https://help.obsidian.md/web-clipper/filters)
+- [Templates](https://help.obsidian.md/web-clipper/templates)
+
+## Examples
+
+See [assets/](assets/) for JSON examples.