skill: teach Datadog dashboard naming conventions

[yordis]

Context

When working on Datadog dashboards in a codebase, the AI should know:

1. Dashboard names in Datadog are owned by the JSON file — the title field in the dashboard JSON is what Datadog displays. Renaming the file alone does nothing; you must update the title field and redeploy.

2. Drop "Dashboard" from the title — everything in Datadog's dashboard list is already a dashboard. [service] Observability Dashboard → [service] Observability.

3. Use [service] prefix convention — scopes the dashboard in Datadog's list which gets crowded fast. Common pattern: [service] Purpose, e.g. [my-service] Observability.

4. Before suggesting a name, check what already exists — run pup dashboards list --yes to see existing names and follow the team's established convention.

Suggested skill.md addition

When working with Datadog dashboard JSON files:

• The title field in the JSON controls the dashboard name in Datadog — not the filename
• Naming convention: [service] Purpose (no "Dashboard" suffix — redundant)
• Always check existing dashboard names via pup dashboards list --yes before proposing a name
• Redeploy after any title change via the deploy script