skills-check

Probe external integrations from project-index.md and infra-{group}.md for reachability and compliance.

6|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/vmkteam/claude-plugins --skill skills-check-vmkteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-check
Source: https://github.com/vmkteam/claude-plugins/tree/main/plugins/developer/skills/skills-check
Command: npx skills add https://github.com/vmkteam/claude-plugins --skill skills-check-vmkteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a lightweight mechanism to verify that external services referenced in project-index.md and infra-{group}.md remain reachable and that pcurl profiles and data-source URLs stay in sync with skill conventions.

Core Features & Use Cases

  • Run probes across YouTrack, GitLab, Sentry, Grafana, Prometheus, Loki, Kibana/OpenSearch, Nomad, and API endpoints to validate reachability and response shapes.
  • Detect changes in API endpoints, expired tokens, or profile mismatches and surface actionable failures.
  • Use case: after provider updates or profile rotations, run /skills-check to confirm all integrations respond as expected.

Quick Start

Run /skills-check to perform all configured integration probes and report any unhealthy data-sources.

Frequently Asked Questions about skills-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I smoke-test data-source integrations for reachability and profile compliance?

To smoke-test data-source integrations, run a parallel probe suite that validates HTTP responses, profile presence, and response shapes across configured endpoints. This surfaces clear pass/fail signals for external services referenced in project-index.md and infra-{group}.md.

Can I verify external services like YouTrack, GitLab, and Sentry connectivity at once?

Yes, you can verify external service connectivity for YouTrack, GitLab, Sentry, Grafana, Prometheus, Loki, Kibana/OpenSearch, Nomad, and API endpoints simultaneously. The skill applies broad and targeted checks across all configured sections.

When should I run integration health checks on my configured data sources?

You should run integration health checks after provider updates or profile rotations to confirm all data sources respond as expected. This detects expired tokens, API endpoint changes, or profile mismatches and surfaces actionable failures.

What is the best way to detect expired tokens and profile mismatches across project infrastructure?

The best way to detect expired tokens and profile mismatches is to execute probes that validate pcurl profiles and data-source URLs against skill conventions. This lightweight mechanism keeps external services in sync and reports unhealthy data sources.

Does this integration check require any external dependencies or components?

No external dependencies or components are required to perform these integration checks. The skill operates as a standalone lightweight mechanism to validate reachability and compliance across your configured data sources.