Menu
Skills in this repository
SkillsMP has collected 56 skills from nartc/dotfiles. Open a skill to review its source and details.
nartc/dotfilesShowing 16 of 56 collected skills.
Use when monitoring Polygraph production health in Grafana, especially nxcloud prod NA, triaging /prepare.data failures, client browser errors, observability gaps, or deciding whether gcx findings warrant Linear follow-up. Do not use for local-only Polygraph…
Use when building throwaway UI, state, logic, interaction, or design probes to answer a specific question before committing to production implementation.
Use when reviewing animation, motion, transitions, Framer Motion/Motion code, CSS animations, hover effects, reduced-motion handling, easing, duration, transform-origin, or animation performance. Don't use for general code review or non-motion UI critique.
Use when the user wants to create a new Grafana resources-as-code project, start a new dashboards-as-code repo, scaffold a gcx project, or asks "how do I get started with gcx". Triggers on phrases like "new project", "scaffold", "bootstrap", "create project",…
Use this skill to set up gcx, configure authentication, establish a connection to a Grafana instance, and complete first-time configuration. This skill covers Grafana Cloud and on-premise deployments, environment variable overrides for CI/CD, default…
Use when creating, editing, adapting, consolidating, validating, or reviewing agent skills, SKILL.md files, skill metadata, source attribution, or discovery behavior. Do not use for normal app documentation or project README work.
Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic…
Use when the user asks about SLO health, wants an overview of all SLOs, or needs status of a specific SLO. Trigger on phrases like "how are my SLOs doing", "SLO status", "check my SLOs", "is my SLO healthy", "SLO budget", "SLO burn rate". For investigating…
Use when a specific SLO is breaching or alerting and the user needs to understand why — root cause analysis, dimensional breakdown, alert rule correlation, runbook access. Trigger on phrases like "investigate SLO", "why is my SLO breaching", "SLO error budget…
Use when the user wants to create, update, pull, push, or delete SLO definitions. Trigger on phrases like "create an SLO", "update SLO objective", "push SLO", "pull SLOs", "delete SLO", or "GitOps sync SLOs". For checking SLO health or status, use…
Use when the user wants to analyze SLO performance trends and receive improvement recommendations — objective tuning, alerting sensitivity review, label visibility, or window adjustments. Trigger on phrases like "optimize my SLO", "SLO improvement…
Use when the user asks about Synthetic Monitoring check health, status, or trends. Trigger on phrases like "are my checks healthy", "check status", "synth check", "probe status", or when users mention specific check names or IDs. For investigating failing…
Use when the user wants to diagnose why a Synthetic Monitoring check is failing — triage probe failures, classify failure scope, run per-probe breakdown, and identify root cause. Trigger on phrases like "why is my check failing", "investigate synthetic…
Use when the user wants to create, update, pull, push, or delete Synthetic Monitoring checks. Trigger on phrases like "create a check", "add a synthetic check", "update check", "pull my SM checks", "push checks", "delete check", or when the user provides a…
Use when reviewing frontend UI, landing pages, dashboards, components, visual polish, spacing, copy hierarchy, interaction quality, or AI-generated generic/slop aesthetics. Don't use for backend/API logic, non-visual refactors, or accessibility-only audits.
Use when a repo, feature, migration, or workstream is too large or foggy for one agent session and needs a durable map of decisions, investigation tickets, frontier work, or repo entry points.