Add powers for New Relic, Splunk, GitHub, GitLab, Grafana, PagerDuty, ServiceNow, and Azure DevOps

[ksravikumar2005]

Summary

Adds POWER.md and steering/steering.md for 8 powers, bringing them to full parity with the existing Datadog and Dynatrace powers. Also adds MIT-0 license and a base-template disclaimer.

Changes

New files created

• splunk/POWER.md + splunk/steering/steering.md
• grafana/POWER.md + grafana/steering/steering.md
• pagerduty/POWER.md + pagerduty/steering/steering.md
• servicenow/POWER.md + servicenow/steering/steering.md
• azure-devops/POWER.md + azure-devops/steering/steering.md
• new-relic/steering/steering.md
• github/steering/steering.md
• gitlab/steering/steering.md
• LICENSE (MIT-0)

Updated files

• new-relic/POWER.md - Added Onboarding section, MCP config placeholders, fixed steering file references
• github/POWER.md - Added Onboarding section, MCP config placeholders, fixed steering file references
• gitlab/POWER.md - Added Onboarding section, MCP config placeholders, fixed steering file references
• README.md - Added Disclaimer section, updated License section to reference MIT-0

What each power includes

• Frontmatter metadata (name, displayName, description, keywords, author)
• Onboarding section with prerequisites, quick start, and MCP config placeholder instructions
• Tool reference with parameters and return types
• Usage examples with realistic queries
• Multi-step workflows combining tools
• Query syntax guides specific to each platform (NRQL, SPL, PromQL/LogQL, WIQL, encoded queries)
• Best practices (do/don't)
• Troubleshooting section
• Configuration/authentication setup
• Security guardrails (credential protection, data sensitivity, access control)
• Anti-hallucination guardrails (query accuracy, result interpretation, tool capability boundaries)
• Operational optimization guardrails (rate limiting, query performance, resource efficiency)
• Cost optimization guardrails (API usage, platform-specific cost awareness, query planning)

Repo-level additions

• MIT-0 license file
• Disclaimer in README stating these are base templates requiring organizational due diligence

Notes

• Keywords were chosen to be specific enough to avoid false-positive activations (e.g., promql instead of metrics, wiql instead of work-items)
• Follows the Kiro Powers framework Pattern B structure (mcp.json + POWER.md + steering/)
• Steering files exceed 500 lines due to guardrails sections, which is acceptable since each file covers a single cohesive domain

[github-actions]

Hi @ksravikumar2005, thank you for your contribution!

Please note that if you haven't already, you would also need to submit your power officially at kiro.dev/powers/submit so it can be reviewed for listing in the Kiro powers registry.