Skill of Skills

Search skills

search_skills

Read-onlyIdempotent

Full-text search over the Skill of Skills directory (AI coding skills, plugins, MCP servers across Claude Code, Cursor, Codex, Windsurf, Cline). Results are ranked by the quality-first composite score, not popularity; when no tool matches every term, the closest partial matches are returned instead (match_mode: "any"), most relevant first. Critical-risk tools are excluded by default (risk_filter); every result carries risk_level and risk_reasons. Scores are evidence, not endorsements.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes	What capability you need, e.g. "postgres migrations"
`min_tier`	No	Quality floor: curated ≥120, promising ≥80, experimental ≥40	experimental
`platform`	No	Restrict to one client platform
`risk_filter`	No	Risk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levels	exclude_critical
`include_high_risk`	No	Deprecated alias for risk_filter=none

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`results`	Yes
`match_mode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "match_mode": {
+      "enum": [
+        "all",
+        "any"
+      ],
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "composite_score": {
+            "type": "number"
+          },
+          "description": {
+            "type": "string"
+          },
+          "is_official": {
+            "type": "boolean"
+          },
+          "last_commit_at": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "platforms": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "profile_url": {
+            "type": "string"
+          },
+          "quality_score": {
+            "type": "number"
+          },
+          "repo_url": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "risk_level": {
+            "type": "string"
+          },
+          "risk_reasons": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "stars": {
+            "type": "number"
+          },
+          "tier": {
+            "enum": [
+              "curated",
+              "promising",
+              "experimental",
+              "review_required"
+            ],
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "slug",
+          "tier",
+          "quality_score",
+          "composite_score",
+          "risk_level",
+          "risk_reasons",
+          "type",
+          "category",
+          "platforms",
+          "description",
+          "repo_url",
+          "profile_url",
+          "stars",
+          "is_official",
+          "last_commit_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "match_mode",
+    "results"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedSep 17, 2026

removedInput schema / properties / include_high_risk / default
```
Removed value: -false
```

changedInput schema / properties / include_high_risk / description

Previous value: -"Also return tools assessed high/critical risk (off by default)"New value: +"Deprecated alias for risk_filter=none"

addedInput schema / properties / risk_filter

Added value: +{
+  "default": "exclude_critical",
+  "description": "Risk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levels",
+  "enum": [
+    "exclude_critical",
+    "exclude_high",
+    "none"
+  ],
+  "type": "string"
+}

First observedJul 13, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive). The description adds valuable behavioral detail: ranking by composite score instead of popularity, partial-match fallback (match_mode: 'any'), default risk filtering, and that results carry risk_level and risk_reasons. This goes beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the primary purpose, then detailing ranking and matching behavior, then risk filtering. No redundant phrases; every sentence contributes to understanding the tool's behavior and output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema and rich annotations, the description covers the essential behavioral aspects: ranking logic, matching mode, risk filtering, and result attributes. It omits minor details like pagination or response format, but these are not critical for the agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (83%), so the baseline is 3. The description adds context around risk_filter and the ranking behavior that affects query handling, but it does not provide per-parameter meaning beyond what the schema already offers (e.g., limit and min_tier are left to the schema). It adds modest value but does not fully compensate for any missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb ('full-text search') and a specific resource (the Skill of Skills directory), and even names the covered platforms and categories. However, it does not explicitly differentiate from sibling tools like get_skill or list_collections, so an agent might not immediately know when to prefer this over a more targeted retrieval tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for searching when you need to find skills by capability, but it does not explicitly state when to use it versus alternatives such as get_skill (for a specific skill) or compare_tools. No exclusions or alternative routing are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Skill of Skills tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.