opencode-skills-collection 4.0.68 → 4.0.70

package/bundled-skills/datadog/SKILL.md

@@ -0,0 +1,487 @@
+---
+name: datadog
+description: Implement Datadog monitoring and APM for infrastructure and applications.
+category: devops
+risk: critical
+source: https://github.com/BagelHole/DevOps-Security-Agent-Skills
+source_repo: BagelHole/DevOps-Security-Agent-Skills
+source_type: community
+date_added: '2026-09-20'
+license: MIT
+license_source: https://github.com/BagelHole/DevOps-Security-Agent-Skills/blob/main/LICENSE
+compatibility: Requires the relevant platform CLIs (kubectl, helm, terraform, git,
+  CI runners) and authorized access to the target environment. Docs-only; helper scripts
+  and templates not bundled.
+metadata:
+  author: devops-skills
+  version: '1.0'
+---
+
+# Datadog
+
+Monitor infrastructure and applications with Datadog's unified observability platform.
+
+## When to Use This Skill
+
+Use this skill when:
+- Implementing enterprise-grade monitoring
+- Setting up APM and distributed tracing
+- Creating unified dashboards for infrastructure and apps
+- Configuring intelligent alerting
+- Monitoring cloud infrastructure (AWS, Azure, GCP)
+
+## Prerequisites
+
+- Datadog account and API key
+- Agent installation access
+- Application code access for APM
+
+## Agent Installation
+
+### Linux
+
+```bash
+# Install agent
+DD_API_KEY=<YOUR_API_KEY> DD_SITE="datadoghq.com" bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_agent7.sh)"
+
+# Or via package manager
+apt-get update && apt-get install datadog-agent
+
+# Configure API key
+echo "api_key: YOUR_API_KEY" >> /etc/datadog-agent/datadog.yaml
+
+# Start agent
+systemctl start datadog-agent
+systemctl enable datadog-agent
+```
+
+### Docker
+
+```yaml
+# docker-compose.yml
+version: '3.8'
+
+services:
+  datadog-agent:
+    image: gcr.io/datadoghq/agent:7
+    environment:
+      - DD_API_KEY=${DD_API_KEY}
+      - DD_SITE=datadoghq.com
+      - DD_LOGS_ENABLED=true
+      - DD_APM_ENABLED=true
+      - DD_PROCESS_AGENT_ENABLED=true
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock:ro
+      - /proc/:/host/proc/:ro
+      - /sys/fs/cgroup/:/host/sys/fs/cgroup:ro
+    ports:
+      - "8126:8126"  # APM
+      - "8125:8125/udp"  # DogStatsD
+```
+
+### Kubernetes
+
+```bash
+# Using Helm
+helm repo add datadog https://helm.datadoghq.com
+
+helm install datadog datadog/datadog \
+  --set datadog.apiKey=${DD_API_KEY} \
+  --set datadog.site=datadoghq.com \
+  --set datadog.logs.enabled=true \
+  --set datadog.apm.portEnabled=true \
+  --set datadog.processAgent.enabled=true \
+  --namespace datadog \
+  --create-namespace
+```
+
+## Agent Configuration
+
+```yaml
+# /etc/datadog-agent/datadog.yaml
+api_key: YOUR_API_KEY
+site: datadoghq.com
+
+# Hostname
+hostname: myserver.example.com
+
+# Tags applied to all metrics
+tags:
+  - env:production
+  - service:myapp
+  - team:platform
+
+# Log collection
+logs_enabled: true
+
+# APM
+apm_config:
+  enabled: true
+  apm_dd_url: https://trace.agent.datadoghq.com
+
+# Process monitoring
+process_config:
+  enabled: true
+
+# Container monitoring
+container_collect_all: true
+docker_labels_as_tags:
+  app: service
+  environment: env
+```
+
+## Integration Configuration
+
+### MySQL
+
+```yaml
+# /etc/datadog-agent/conf.d/mysql.d/conf.yaml
+init_config:
+
+instances:
+  - host: localhost
+    port: 3306
+    username: datadog
+    password: <PASSWORD>
+    tags:
+      - env:production
+    options:
+      replication: true
+      extra_status_metrics: true
+```
+
+### PostgreSQL
+
+```yaml
+# /etc/datadog-agent/conf.d/postgres.d/conf.yaml
+init_config:
+
+instances:
+  - host: localhost
+    port: 5432
+    username: datadog
+    password: <PASSWORD>
+    dbname: mydb
+    collect_activity_metrics: true
+    collect_database_size_metrics: true
+```
+
+### NGINX
+
+```yaml
+# /etc/datadog-agent/conf.d/nginx.d/conf.yaml
+init_config:
+
+instances:
+  - nginx_status_url: http://localhost:80/nginx_status
+    tags:
+      - env:production
+```
+
+## Log Collection
+
+### File-Based Logs
+
+```yaml
+# /etc/datadog-agent/conf.d/myapp.d/conf.yaml
+logs:
+  - type: file
+    path: /var/log/myapp/*.log
+    service: myapp
+    source: python
+    sourcecategory: custom
+    tags:
+      - env:production
+
+  - type: file
+    path: /var/log/nginx/access.log
+    service: nginx
+    source: nginx
+    log_processing_rules:
+      - type: exclude_at_match
+        name: exclude_healthchecks
+        pattern: health_check
+```
+
+### Docker Logs
+
+```yaml
+# docker-compose.yml
+services:
+  myapp:
+    labels:
+      com.datadoghq.ad.logs: '[{"source": "python", "service": "myapp"}]'
+```
+
+### Kubernetes Logs
+
+```yaml
+# Pod annotation
+apiVersion: v1
+kind: Pod
+metadata:
+  annotations:
+    ad.datadoghq.com/myapp.logs: |
+      [{
+        "source": "python",
+        "service": "myapp",
+        "log_processing_rules": [{
+          "type": "multi_line",
+          "name": "python_tracebacks",
+          "pattern": "^Traceback"
+        }]
+      }]
+```
+
+## APM Configuration
+
+### Python
+
+```python
+from ddtrace import patch_all, tracer
+
+# Automatic instrumentation
+patch_all()
+
+# Configure tracer
+tracer.configure(
+    hostname='localhost',
+    port=8126,
+    service='myapp',
+    env='production',
+    version='1.0.0'
+)
+
+# Manual instrumentation
+@tracer.wrap(service='myapp', resource='process_order')
+def process_order(order_id):
+    with tracer.trace('validate_order') as span:
+        span.set_tag('order_id', order_id)
+        # Validation logic
+    
+    with tracer.trace('save_order'):
+        # Save logic
+        pass
+```
+
+```bash
+# Install library
+pip install ddtrace
+
+# Run with auto-instrumentation
+ddtrace-run python app.py
+```
+
+### Node.js
+
+```javascript
+const tracer = require('dd-trace').init({
+  service: 'myapp',
+  env: 'production',
+  version: '1.0.0',
+  logInjection: true
+});
+
+// Manual instrumentation
+const span = tracer.startSpan('custom_operation');
+span.setTag('user_id', userId);
+// ... operation
+span.finish();
+```
+
+```bash
+# Install library
+npm install dd-trace
+
+# Run with auto-instrumentation
+DD_TRACE_ENABLED=true node --require dd-trace/init app.js
+```
+
+### Go
+
+```go
+import (
+    "gopkg.in/DataDog/dd-trace-go.v1/ddtrace/tracer"
+)
+
+func main() {
+    tracer.Start(
+        tracer.WithService("myapp"),
+        tracer.WithEnv("production"),
+        tracer.WithServiceVersion("1.0.0"),
+    )
+    defer tracer.Stop()
+
+    // Manual span
+    span, ctx := tracer.StartSpanFromContext(ctx, "process_request")
+    defer span.Finish()
+    span.SetTag("user_id", userID)
+}
+```
+
+## Custom Metrics
+
+### DogStatsD
+
+```python
+from datadog import DogStatsd
+
+statsd = DogStatsd(host='localhost', port=8125)
+
+# Counter
+statsd.increment('myapp.orders.count', tags=['env:production'])
+
+# Gauge
+statsd.gauge('myapp.queue.size', queue_size, tags=['queue:orders'])
+
+# Histogram
+statsd.histogram('myapp.request.duration', response_time)
+
+# Distribution
+statsd.distribution('myapp.response_time', duration, tags=['endpoint:/api/orders'])
+```
+
+### API Submission
+
+```python
+from datadog_api_client import Configuration, ApiClient
+from datadog_api_client.v2.api.metrics_api import MetricsApi
+from datadog_api_client.v2.model.metric_payload import MetricPayload
+from datadog_api_client.v2.model.metric_series import MetricSeries
+from datadog_api_client.v2.model.metric_point import MetricPoint
+
+configuration = Configuration()
+with ApiClient(configuration) as api_client:
+    api = MetricsApi(api_client)
+    
+    payload = MetricPayload(
+        series=[
+            MetricSeries(
+                metric="custom.metric.name",
+                type=MetricSeries.GAUGE,
+                points=[MetricPoint(value=42.0, timestamp=int(time.time()))],
+                tags=["env:production"]
+            )
+        ]
+    )
+    api.submit_metrics(body=payload)
+```
+
+## Dashboards
+
+### Dashboard JSON
+
+```json
+{
+  "title": "Application Overview",
+  "widgets": [
+    {
+      "definition": {
+        "type": "timeseries",
+        "title": "Request Rate",
+        "requests": [
+          {
+            "q": "sum:trace.http.request.hits{service:myapp}.as_rate()",
+            "display_type": "line"
+          }
+        ]
+      }
+    },
+    {
+      "definition": {
+        "type": "query_value",
+        "title": "Error Rate",
+        "requests": [
+          {
+            "q": "sum:trace.http.request.errors{service:myapp}.as_rate() / sum:trace.http.request.hits{service:myapp}.as_rate() * 100"
+          }
+        ],
+        "precision": 2
+      }
+    }
+  ]
+}
+```
+
+## Monitors (Alerts)
+
+### Metric Monitor
+
+```json
+{
+  "name": "High Error Rate",
+  "type": "metric alert",
+  "query": "sum(last_5m):sum:trace.http.request.errors{service:myapp}.as_count() / sum:trace.http.request.hits{service:myapp}.as_count() > 0.05",
+  "message": "Error rate is {{value}}% for {{service.name}}. @slack-alerts",
+  "tags": ["service:myapp", "env:production"],
+  "options": {
+    "thresholds": {
+      "critical": 0.05,
+      "warning": 0.02
+    },
+    "notify_no_data": true,
+    "no_data_timeframe": 10
+  }
+}
+```
+
+### APM Monitor
+
+```json
+{
+  "name": "High Latency Alert",
+  "type": "trace-analytics alert",
+  "query": "trace-analytics(\"service:myapp @http.status_code:2*\").rollup(\"avg\", \"@duration\").last(\"5m\") > 2000000000",
+  "message": "Average latency is above 2 seconds. @pagerduty",
+  "options": {
+    "thresholds": {
+      "critical": 2000000000
+    }
+  }
+}
+```
+
+## Common Issues
+
+### Issue: Agent Not Reporting
+**Problem**: No data appearing in Datadog
+**Solution**: Check API key, verify agent status with `datadog-agent status`
+
+### Issue: Missing Traces
+**Problem**: APM traces not appearing
+**Solution**: Verify APM is enabled, check tracer configuration, verify port 8126
+
+### Issue: High Cardinality Tags
+**Problem**: Custom metrics getting dropped
+**Solution**: Reduce unique tag values, use distributions instead of histograms
+
+## Best Practices
+
+- Use consistent service and environment tags
+- Implement proper tag naming conventions
+- Use unified service tagging (service, env, version)
+- Set up service-level monitors
+- Create dashboards per service
+- Implement log correlation with traces
+- Use distributions for latency metrics
+- Configure proper alert escalation
+
+## Related Skills
+
+- prometheus-grafana (`prometheus-grafana`) - Open source alternative
+- alerting-oncall (`alerting-oncall`) - Alert management
+- aws-vpc (`aws-vpc`) - AWS monitoring
+
+## Limitations
+
+- Guidance executes against real environments: confirm target, blast radius, and rollback plan before applying anything.
+- Never deploy to production without explicit approval. Docs-only import: upstream scripts and templates not bundled.
+
+### Example
+
+```bash
+git status && git diff --stat
+kubectl diff -f manifest.yaml
+```
+
+> Adapted from [BagelHole/DevOps-Security-Agent-Skills](https://github.com/BagelHole/DevOps-Security-Agent-Skills) (MIT); frontmatter, When to Use/Limitations, and safety boundaries added for upstream compliance. Docs-only import: helper scripts and templates not bundled.

package/bundled-skills/dependency-analysis/README.md

@@ -0,0 +1,42 @@
+# Dependency Analysis
+
+This is an official Ontoly Agent Skill. It is independently installable and teaches an agent how to use Ontoly for dependency analysis.
+
+## Version
+
+- Skill version: 1.0.0
+- Minimum Ontoly version: 1.0.0
+- Required capabilities: `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics`, `EvidencePack`
+- Enhancement: LLM Enhancement
+- Deprecated: no
+
+## Install
+
+Install this skill with any Agent Skills compatible installer that supports `SKILL.md` directories, or copy this folder into your agent skills directory.
+
+## Use
+
+Ask the agent a task such as:
+
+> Which packages depend on this module?
+
+The agent should build or verify the Ontoly graph, use MCP capabilities, cite evidence, and only inspect files as a fallback.
+
+## Public Docs
+
+- [Agent Skills](https://ontoly.xyz/docs/agent-skills)
+- [Skills Overview](https://ontoly.xyz/docs/skills-overview)
+- [MCP](https://ontoly.xyz/docs/mcp)
+- [Capabilities](https://ontoly.xyz/docs/capabilities)
+- [Skills Validation](https://ontoly.xyz/docs/skills-validation)
+
+## Shared References
+
+This skill depends on the shared Ontoly workflow in [reference/workflow.md](reference/workflow.md).
+
+## Learn more
+
+- Documentation: https://ontoly.xyz/docs
+- This skill on the web: https://ontoly.xyz/skills#dependency-analysis
+- All Ontoly Agent Skills: https://ontoly.xyz/skills
+- Install via skills.sh: https://www.skills.sh/?q=0xsarwagya/ontoly

package/bundled-skills/dependency-analysis/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: dependency-analysis
+description: Analyze internal and package dependencies using Ontoly graph traversal.
+  Use when asked which modules, packages, services, or files depend on each other.
+license: AGPL-3.0-only
+compatibility: Portable Agent Skills format; requires Ontoly CLI and MCP-capable or
+  CLI-capable coding agent.
+metadata:
+  ontoly.skill.version: 1.3.3
+  ontoly.min.version: 1.3.3
+  ontoly.capabilities: FindDependencies, FindDependents, FindCycles, GraphStatistics,
+    EvidencePack
+  ontoly.category: dependencies
+  ontoly.enhancement: LLM Enhancement
+  ontoly.deprecated: 'false'
+source_repo: 0xsarwagya/ontoly
+source_type: community
+source: community
+date_added: '2026-09-21'
+risk: unknown
+---
+## When to Use
+- Use when this upstream workflow matches the user's stated goal.
+- Use when the task requires the procedures documented in this skill.
+
+# Dependency Analysis
+
+Use this skill when the user asks for dependency analysis using Ontoly evidence.
+
+## Required Workflow
+
+Follow [the shared Ontoly workflow. Also read [graph evidence rules, [MCP usage, [best practices, and [fallback rules when the task requires detail.
+
+## Ontoly Capabilities
+
+Use these capabilities first: `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics`, `EvidencePack`.
+
+## Output Contract
+
+Return:
+
+- answer or plan
+- capabilities invoked
+- graph evidence with node ids, edge types, source spans, and graph hash when available
+- confidence: high, medium, or low
+- fallback reason if repository files were inspected
+
+## Boundaries
+
+Do not implement compiler, query, MCP, SDK, or business logic in the skill. Do not search repository files until Ontoly cannot answer or evidence must be confirmed.
+
+## Resources
+
+- [Examples
+- [Prompt template
+- [Capability notes
+
+## Learn more
+
+- Documentation: https://ontoly.xyz/docs
+- This skill on the web: https://ontoly.xyz/skills#dependency-analysis
+- All Ontoly Agent Skills: https://ontoly.xyz/skills
+- Install via skills.sh: https://www.skills.sh/?q=0xsarwagya/ontoly
+
+
+## Examples
+
+```text
+User: Apply this skill to my current task.
+Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
+```
+
+## Limitations
+
+- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
+- Does not replace environment-specific validation, testing, or maintainer review.

package/bundled-skills/dependency-analysis/examples.md

@@ -0,0 +1,11 @@
+# Dependency Analysis Examples
+
+Each example is graph-first and MCP-first.
+
+| Repository | Questions | Expected workflow | Capabilities invoked | Expected evidence | Expected answer |
+| --- | --- | --- | --- | --- | --- |
+| Ovok Core | Trace the login flow through the NestJS auth controller. | Follow shared workflow, run `EvidencePack` first, then `FindDependencies` then `FindDependents` then `FindCycles` then `GraphStatistics`, inspect files only if graph evidence is missing. | `EvidencePack`, `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics` | controller, route, service, dependency-injection edges; graph hash; confidence. | A deterministic dependency report with direct/transitive edges, cycles, and confidence. |
+| Ghost | Explain the package entrypoint and public API surface. | Follow shared workflow, run `EvidencePack` first, then `FindDependencies` then `FindDependents` then `FindCycles` then `GraphStatistics`, inspect files only if graph evidence is missing. | `EvidencePack`, `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics` | package, exports, functions, interfaces; graph hash; confidence. | A deterministic dependency report with direct/transitive edges, cycles, and confidence. |
+| durable-local | Find storage APIs and consumers before a refactor. | Follow shared workflow, run `EvidencePack` first, then `FindDependencies` then `FindDependents` then `FindCycles` then `GraphStatistics`, inspect files only if graph evidence is missing. | `EvidencePack`, `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics` | functions, interfaces, dependents, configuration; graph hash; confidence. | A deterministic dependency report with direct/transitive edges, cycles, and confidence. |
+| 0xsarwagya | Summarize workspace packages and package dependencies. | Follow shared workflow, run `EvidencePack` first, then `FindDependencies` then `FindDependents` then `FindCycles` then `GraphStatistics`, inspect files only if graph evidence is missing. | `EvidencePack`, `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics` | workspace, packages, framework nodes, dependency edges; graph hash; confidence. | A deterministic dependency report with direct/transitive edges, cycles, and confidence. |
+| Innosphere | Identify application modules and request ownership. | Follow shared workflow, run `EvidencePack` first, then `FindDependencies` then `FindDependents` then `FindCycles` then `GraphStatistics`, inspect files only if graph evidence is missing. | `EvidencePack`, `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics` | controllers, modules, routes, services; graph hash; confidence. | A deterministic dependency report with direct/transitive edges, cycles, and confidence. |

package/bundled-skills/dependency-analysis/reference/best-practices.md

@@ -0,0 +1,7 @@
+# Agent Best Practices
+
+- Keep the answer graph-first and concise.
+- Separate measured graph facts from inference.
+- Prefer capability output over source search.
+- Include confidence: high when graph nodes and relationships directly answer the question, medium when evidence is partial, low when fallback file inspection was required.
+- Never generate SDKs, refactors, or security claims from the skill itself. The skill may plan workflows, but Ontoly remains the source of truth.

package/bundled-skills/dependency-analysis/reference/capabilities.md

@@ -0,0 +1,20 @@
+# Dependency Analysis Capability Notes
+
+Primary capabilities: `FindDependencies`, `FindDependents`, `FindCycles`, `GraphStatistics`, `EvidencePack`.
+
+Use [../reference/mcp.md](../reference/mcp.md) for common capability behavior and fallback CLI equivalents.
+
+## Required Evidence
+
+- capability name
+- graph hash
+- node ids and types
+- relationship types and direction
+- source spans when present
+- confidence
+
+## Compatibility
+
+- Skill version: 1.0.0
+- Minimum Ontoly version: 1.0.0
+- Deprecation status: active

package/bundled-skills/dependency-analysis/reference/fallbacks.md

@@ -0,0 +1,11 @@
+# Fallbacks
+
+Fallbacks are allowed only after Ontoly is insufficient. Valid fallback reasons:
+
+- graph artifact missing and build fails
+- relevant capability unavailable
+- graph trust below the task threshold
+- node is ambiguous or absent
+- source quote is needed to confirm a public answer
+
+When falling back, state the reason and keep inspection narrow: one file, one symbol, or one source span when possible.

package/bundled-skills/dependency-analysis/reference/graph.md

@@ -0,0 +1,15 @@
+# Software Graph Evidence
+
+Use Software Graph evidence as the primary source of truth. Prefer deterministic identifiers over prose names.
+
+Evidence fields to capture:
+
+- graph hash
+- capability invoked
+- node id and node type
+- edge type and direction
+- source span when present
+- diagnostic codes when relevant
+- confidence and reason for confidence
+
+Do not infer relationships that are absent from the graph. You may make a clearly labeled inference only after stating the graph evidence that supports it.

package/bundled-skills/dependency-analysis/reference/mcp.md

@@ -0,0 +1,14 @@
+# Ontoly MCP Usage
+
+Use Ontoly MCP capabilities before searching files. Common capability groups:
+
+- Architecture: `ExplainArchitecture`, `GraphStatistics`
+- Lookup: `FindNode`, `FindFunction`, `InspectFile`, `InspectModule`, `InspectClass`, `InspectFunction`
+- Dependencies: `FindDependencies`, `FindDependents`, `FindCycles`, `ImpactAnalysis`
+- Requests: `TraceRequestLifecycle`, `FindResponsibleFunction`, `TraceExecution`
+- Security: `FindAuthenticationFlow`, `FindConfigurationUsage`
+- Configuration: `FindConfiguration`, `FindConfigurationUsage`
+- Static analysis: `FindDeadCode`, `FindUnusedFeature`, `FindEntrypoints`
+- Evidence packs: `EvidencePack`
+
+If an agent cannot call MCP directly, use the nearest CLI command such as `ontoly evidence`, `ontoly report`, `ontoly query`, `ontoly trace`, or `ontoly inspect`.