MaTE Logo
MaTE Skills
SearchCollectionsCompareChangelogPricing
Agents:claude-codecodexcopilot
MaTE Skills — discovery, trust & activation for agent skills. Powered by Rainy MaTE
CollectionsSearchChangelogskills.sh

Comparison.

Evaluating analyze-skill-issues vs test-fixing

Subject A
analyze-skill-issues
Community
Subject B
test-fixing
Community
Decision Engine64% Confidence

analyze-skill-issues

analyze-skill-issues is the safer starting point, but both options need closer inspection.

analyze-skill-issues has the stronger blended fit for this context.analyze-skill-issues is safer or more trusted than test-fixing for the current team posture.Compatibility should still be validated in the target agent.
Score breakdown
analyze-skill-issues
Trust100%
Safety95%
Freshness80%
Compat100%
test-fixing
Trust95%
Safety95%
Scenario Recommendations
Strict security environment
analyze-skill-issues
analyze-skill-issues has lower risk (0.05 vs 0.05) and fewer static signal flags.
Rapidly evolving projects
analyze-skill-issues
analyze-skill-issues has a higher freshness score (80%) indicating more recent maintenance.
Description
Query the integration-test storage account to find why a specific skill's tests are failing. Reads blob-stored test result files and surfaces error details. TRIGGERS: why is skill failing, skill test failures, debug skill tests, skill failing tests, analyze skill failures, why are tests failing for skill, skill test errors, investigate skill issues. DO NOT USE FOR: analyzing a GitHub Actions run report or comparing test runs across runs (use analyze-test-run).
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests (\"fix these tests\", \"make tests pass\"), reports test failures (\"tests are failing\", \"test suite is broken\"), or completes implementation and wants tests passing.
Risk Evaluation
Low risk
Low risk
Trust Score
100%
Trust100%

Deep Synthesis Engine

AI-powered deep comparison with scenario-based recommendations, trust analysis, and per-skill strengths. (2 credits)

Activation Vectors

analyze-skill-issues
test-fixing
Freshness80%
Compat100%
95%
Trust95%
Freshness Matrix
80%
Freshness80%
80%
Freshness80%
Security Signals
SignalAB
HTML comments✓✓
Remote exec✓✓
Network calls✓✓
Shell mutation✓✓
Sensitive files✓✓
Missing license✕✕
✓ = clean✕ = flagged
Both share: missing license. Installing either carries these signals.
Agent Compatibility
AGENTAB
claude-codeinferredinferred
codexinferredinferred
copilotinferredinferred
gemini-cliinferredinferred
cursorinferredinferred
windsurfinferredinferred
License Strictness
MIT
No License
Optimal Context
- User asks why a skill's tests are failing - User asks to debug or investigate a skill's recent test failures - User wants to see errors from integration test runs for a specific skill - User asks what errors or exceptions caused skill test failures
- Explicitly asks to fix tests ("fix these tests", "make tests pass") - Reports test failures ("tests are failing", "test suite is broken") - Completes implementation and wants tests passing - Mentions CI/CD failures due to tests