AB china-check
Look up and verify mainland-China (PRC) companies from official GSXT/SAMR registration data. Use whenever the user wants to find, verify, vet, or research a Chinese company, supplier, factory, manufacturer, brand, or business partner — or asks for a company's legal name, legal representative, registration status, Unified Social Credit Code (USCC), registered capital, registered address, business scope, or industry. Backed by the free China-Check MCP server (search_chinese_company + get_company_snapshot).
Look up and verify mainland-China (PRC) companies from official GSXT/SAMR registration data.
As a process B 68/100 · Nearly there — weak spots: result and completion, consistency, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 68/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (china-check) differs from the folder (china-company-check-mcp)
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Execution cost. Instruction body is 988 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 509: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 21 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.