SKILLEMALL.ai
GitHub ↗ RU Sign in

BC nyne-search

Search for people using natural language queries with the Nyne Search API. Find professionals by role, company, location, industry, or any combination. Supports custom filters, AI relevance scoring, contact enrichment (emails + phones), pagination, and three search tiers (light, medium, premium). Async with polling.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 7 112 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Search for people using natural language queries with the Nyne Search API.

As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

IntegrationAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
C
64/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 7112 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 64/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 7112 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 14 top-level sections: this looks like several domains in one skill

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 317: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 21 items
  • +3Output format is stated explicitly
  • +4Has examples (28 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.