Agent skill · DevOps & Cloud

signal-party

Parallel metrics collection using G-6 SIGNAL. Deploy 6 probes to gather metrics from all sources for data-driven decisions.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill signal-party --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 16 KB
Bundled scripts: none
Path: skills/analysis/signal-party/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SIGNAL_PARTY Skill > **Purpose:** Coordinated parallel metrics collection with 6 specialized probes > **Created:** 2026-01-06 > **Trigger:** `/signal-party` command > **Aliases:** `/signal`, `/metrics`, `/sp6` > **Owner:** G6_SIGNAL (G-6 Staff) --- ## When to Use Deploy SIGNAL_PARTY when you need comprehensive metrics intelligence: - Performance analysis for schedules or system health - Data-driven decision support for strategic planning - Resilience framework health assessment - Trend analysis and anomaly detection - Pre-deployment validation metrics - Evidence collection for compliance reviews - System health monitoring and diagnostics **Do NOT use for:** - Simple single-metric queries (use direct MCP tool calls) - When only one lens is needed - Interpreting data (SIGNAL collects, doesn't recommend) --- ## Economics: Zero Marginal Wall-Clock Cost **Critical Understanding:** Parallel agents with the same timeout cost nothing extra in wall-clock time. ``` Sequential (BAD): Parallel (GOOD): 6 probes × 60s each 6 probes × 60s in parallel Total: 360s Total: 60s (6x faster) ``` **Implication:** Always spawn all probes. There is no cost savings from running fewer. --- ## The Six Probe

What's inside
Steps it walks through
  1. When to Use
  2. Economics: Zero Marginal Wall-Clock Cost
  3. The Six Probes
  4. Probe Details
  5. Deployment Pattern
  6. Standard Deployment: 6 SIGNAL Probes
  7. Invocation
  8. Full Deployment (6 probes)
  9. Targeted Deployment (specific domain)
  10. Quick Metrics (3 critical probes)
  11. IDE Crash Prevention (CRITICAL)
  12. Spawn Pattern
  13. Via G6SIGNAL Commander (CORRECT)
  14. Direct Deployment (Only if G6SIGNAL unavailable)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the signal-party skill do?

Parallel metrics collection using G-6 SIGNAL. Deploy 6 probes to gather metrics from all sources for data-driven decisions.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill signal-party --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going