skill-diagnostic

Validates skill discovery, loading, and distribution pipeline with a fixed response protocol.

24|7|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/qiaolei227/opendeploy --skill skill-diagnostic-qiaolei227
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-diagnostic
Source: https://github.com/qiaolei227/opendeploy/tree/main/knowledge/skills/system/skill-diagnostic
Command: npx skills add https://github.com/qiaolei227/opendeploy --skill skill-diagnostic-qiaolei227

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When setting up or troubleshooting the OpenDeploy skill subsystem, you need a quick way to confirm that skills are actually discovered, loaded, and delivered to the agent — not just listed in a catalog. This Skill provides a deterministic self-check that proves the entire skill pipeline is wired correctly. ## Core Features & Use Cases - Activation Verification: Returns a fixed first-line marker proving the skill body was loaded into context, not just its description. - Pipeline Coverage Check: Confirms three capabilities — skill discovery from the system prompt catalog, skill loading via the load_skill tool, and skill distribution via installer seed or git pull. - Source Reporting: States where the skill body was loaded from (local seed package, GitHub repository, or Gitee mirror). - Use Case: After installing OpenDeploy or updating the knowledge base, type "/skill-ping" to verify the skill subsystem works end to end before relying on business skills. ## Quick Start Ask the agent to run a skill system test by typing "/skill-ping" or "测试技能激活" and check that the response begins with the exact activation marker line.

Frequently Asked Questions about skill-diagnostic

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

FAQPage Schema
How do I test if the skill system is working?▼

Type "/skill-ping" or ask the agent to test skill activation. The agent loads this diagnostic skill and must reply with a fixed marker line proving the skill body reached its context.

What does the skill-diagnostic activation check verify?▼

It verifies three capabilities: skill discovery from the system prompt catalog, skill loading through the load_skill tool, and skill distribution via installer seed packages or git pulls from GitHub or Gitee.

When should I use the skill diagnostic tool?▼

Use it only when explicitly testing the skill subsystem, such as after installation or a knowledge base update. It is a verification utility and should not be triggered during normal business conversations.

Why does the diagnostic response start with a fixed marker line?▼

The fixed first line proves the skill body was actually loaded into the agent's context rather than only its catalog description. Any deviation indicates the loading pipeline is broken.

Can skill-diagnostic answer business or ERP questions?▼

No. It is purely a diagnostic tool for the skill pipeline and explicitly instructs the agent to ignore it for business scenarios. Use the domain skills for ERP implementation tasks.