Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Notion API Skill · aiskillstore | DecimalAI

aiskillstore/notion-api

SkillScore84Maintained

This skill should be used when the user asks to "search Notion", "find in Notion", "search my Notion workspace", "create Notion page", "make a Notion page", "update Notion page", "edit Notion page", "query Notion database", "get Notion database", "read Notion page", "get page content from Notion", "list Notion pages", or mentions Notion integration, Notion workspace, or Notion API access.

productivityby aiskillstore

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Knowledge Management pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/aiskillstore-notion-api/SKILL.md

decimalai skills pull aiskillstore-notion-api --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/aiskillstore-notion-api/SKILL.md https://app.decimal.ai/s/aiskillstore-notion-api/SKILL.md

Raw file: /s/aiskillstore-notion-api/SKILL.md ↗ · machine-readable summary at /s/aiskillstore-notion-api.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

25 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 19d ago

Yes — +36% lift · at higher cost+311% tokens0% turns84% of whole cases pass with skill (21/25)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-05	✗→✓	▲ Improved	170%	0%
case-07	✗→✓	▲ Improved	477%	0%
case-08	✗→✓	▲ Improved	239%	0%
case-11	✗→✓	▲ Improved	120%	0%
case-15	✗→✓	▲ Improved	556%	0%

Showing 5 of 25 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 8/26/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

aiskillstore / marketplace

skills/bltgv/notion-api/SKILL.md

View on GitHub ↗

Imported 8/26/2026Version v2Bundled 4 files

Skill contents

references/

SKILL.md

Notion API Skill

This skill enables interaction with Notion workspaces through the Notion REST API. Use curl and jq for direct REST calls, or write ad-hoc scripts as appropriate for the task.

Authentication

API Key Handling

Environment Variable: Check if NOTION_API_TOKEN is available in the environment
User-Provided Key: If the user provides an API key in context, use that instead
No Key Available: If neither is available, use AskUserQuestion (or equivalent) to request the API key from the user

IMPORTANT: Never display, log, or send NOTION_API_TOKEN anywhere except in the Authorization header. Confirm its existence, ask if missing, use it in requests—but never echo or expose it.

Request Headers

All requests require these headers:

bash
-H "Authorization: Bearer $NOTION_API_TOKEN" \
-H "Notion-Version: 2025-09-03" \
-H "Content-Type: application/json"

Verifying Authentication

Test the API key by retrieving the bot user:

bash
curl -s "https://api.notion.com/v1/users/me" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Base URL and Conventions

Base URL: https://api.notion.com
API Version: 2025-09-03 (required header)
Data Format: JSON for all request/response bodies
IDs: UUIDv4 format (dashes optional in requests)
Timestamps: ISO 8601 format (2020-08-12T02:12:33.231Z)
Property Names: snake_case
Empty Values: Use null instead of empty strings

Rate Limits

Average: 3 requests per second per integration
Bursts: Brief bursts above this limit are allowed
Rate Limited Response: HTTP 429 with Retry-After header
Strategy: Implement exponential backoff when receiving 429 responses

Request Size Limits

| Type | Limit | |------|-------| | Maximum block elements per payload | 1000 | | Maximum payload size | 500KB | | Rich text content | 2000 characters | | URLs | 2000 characters | | Equations | 1000 characters | | Email addresses | 200 characters | | Phone numbers | 200 characters | | Multi-select options | 100 items | | Relations | 100 related pages | | People mentions | 100 users | | Block arrays per request | 100 elements |

Confirmation for Destructive Operations

IMPORTANT: Before executing any operation that modifies or deletes data, ask the user for confirmation. This includes:

Updating pages or blocks
Deleting/archiving pages or blocks
Modifying database schemas
Creating pages (if multiple or in batch)
Any bulk operations

For a logical group of related operations, a single confirmation is sufficient.

Core API Endpoints

Search

Search across all accessible pages and databases:

bash
curl -s -X POST "https://api.notion.com/v1/search" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "search term",
    "filter": {"property": "object", "value": "page"},
    "sort": {"direction": "descending", "timestamp": "last_edited_time"},
    "page_size": 100
  }' | jq

Filter values: "page" or "data_source" (or omit for both)

Pages

Retrieve a Page

bash
curl -s "https://api.notion.com/v1/pages/{page_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Note: This returns page properties, not content. For content, use "Retrieve block children" with the page ID.

Create a Page

bash
curl -s -X POST "https://api.notion.com/v1/pages" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "parent": {"page_id": "parent-page-id"},
    "properties": {
      "title": {
        "title": [{"text": {"content": "Page Title"}}]
      }
    },
    "children": [
      {
        "object": "block",
        "type": "paragraph",
        "paragraph": {
          "rich_text": [{"type": "text", "text": {"content": "Paragraph content"}}]
        }
      }
    ]
  }' | jq

Parent options:

{"page_id": "..."} - Create under a page
{"database_id": "..."} - Create in a database (legacy)
{"data_source_id": "..."} - Create in a data source (API v2025-09-03+)

Update a Page

bash
curl -s -X PATCH "https://api.notion.com/v1/pages/{page_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "properties": {
      "title": {"title": [{"text": {"content": "Updated Title"}}]}
    },
    "icon": {"type": "emoji", "emoji": "📝"},
    "archived": false
  }' | jq

Additional update options: cover, is_locked, in_trash

Archive (Delete) a Page

bash
curl -s -X PATCH "https://api.notion.com/v1/pages/{page_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{"archived": true}' | jq

Retrieve a Page Property Item

For properties with more than 25 references:

bash
curl -s "https://api.notion.com/v1/pages/{page_id}/properties/{property_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Blocks (Page Content)

Retrieve Block Children

bash
curl -s "https://api.notion.com/v1/blocks/{block_id}/children?page_size=100" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Use the page ID as block_id to get page content. Check has_children on each block for nested content.

Append Block Children

bash
curl -s -X PATCH "https://api.notion.com/v1/blocks/{block_id}/children" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "children": [
      {
        "object": "block",
        "type": "heading_2",
        "heading_2": {
          "rich_text": [{"type": "text", "text": {"content": "New Section"}}]
        }
      },
      {
        "object": "block",
        "type": "paragraph",
        "paragraph": {
          "rich_text": [{"type": "text", "text": {"content": "Content here"}}]
        }
      }
    ]
  }' | jq

Maximum 100 blocks per request, up to 2 levels of nesting.

Position options in request body:

Default: appends to end
"position": {"type": "start"} - Insert at beginning
"position": {"type": "after_block", "after_block": {"id": "block-id"}} - Insert after specific block

Retrieve a Block

bash
curl -s "https://api.notion.com/v1/blocks/{block_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Update a Block

bash
curl -s -X PATCH "https://api.notion.com/v1/blocks/{block_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "paragraph": {
      "rich_text": [{"type": "text", "text": {"content": "Updated content"}}]
    }
  }' | jq

The update replaces the entire value for the specified field.

Delete a Block

bash
curl -s -X DELETE "https://api.notion.com/v1/blocks/{block_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Moves block to trash (can be restored).

Databases

Retrieve a Database

bash
curl -s "https://api.notion.com/v1/databases/{database_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Returns database structure including data sources and properties.

Query a Database

bash
curl -s -X POST "https://api.notion.com/v1/databases/{database_id}/query" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "filter": {
      "property": "Status",
      "select": {"equals": "Done"}
    },
    "sorts": [
      {"property": "Created", "direction": "descending"}
    ],
    "page_size": 100
  }' | jq

See references/filters-and-sorts.md for comprehensive filter and sort documentation.

Create a Database

bash
curl -s -X POST "https://api.notion.com/v1/databases" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "parent": {"page_id": "parent-page-id"},
    "title": [{"type": "text", "text": {"content": "My Database"}}],
    "is_inline": true,
    "initial_data_source": {
      "properties": {
        "Name": {"title": {}},
        "Status": {
          "select": {
            "options": [
              {"name": "To Do", "color": "red"},
              {"name": "In Progress", "color": "yellow"},
              {"name": "Done", "color": "green"}
            ]
          }
        },
        "Due Date": {"date": {}}
      }
    }
  }' | jq

Update a Database

bash
curl -s -X PATCH "https://api.notion.com/v1/databases/{database_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "title": [{"text": {"content": "Updated Title"}}],
    "description": [{"text": {"content": "Database description"}}]
  }' | jq

Data Sources (API v2025-09-03+)

Data sources are individual tables within a database. As of API version 2025-09-03, databases can contain multiple data sources.

Create a Data Source

bash
curl -s -X POST "https://api.notion.com/v1/data_sources" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "parent": {"type": "database_id", "database_id": "database-id"},
    "title": [{"type": "text", "text": {"content": "New Data Source"}}],
    "properties": {
      "Name": {"title": {}},
      "Description": {"rich_text": {}}
    }
  }' | jq

Users

List All Users

bash
curl -s "https://api.notion.com/v1/users?page_size=100" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Retrieve a User

bash
curl -s "https://api.notion.com/v1/users/{user_id}" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Retrieve Bot User (Self)

bash
curl -s "https://api.notion.com/v1/users/me" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Comments

Retrieve Comments

bash
curl -s "https://api.notion.com/v1/comments?block_id={block_id}&page_size=100" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" | jq

Use a page ID as block_id for page-level comments.

Create a Comment

On a page:

bash
curl -s -X POST "https://api.notion.com/v1/comments" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "parent": {"page_id": "page-id"},
    "rich_text": [{"type": "text", "text": {"content": "Comment content"}}]
  }' | jq

Reply to a discussion:

bash
curl -s -X POST "https://api.notion.com/v1/comments" \
  -H "Authorization: Bearer $NOTION_API_TOKEN" \
  -H "Notion-Version: 2025-09-03" \
  -H "Content-Type: application/json" \
  -d '{
    "discussion_id": "discussion-id",
    "rich_text": [{"type": "text", "text": {"content": "Reply content"}}]
  }' | jq

Note: The API cannot start new inline discussion threads or edit/delete existing comments.

Pagination

Paginated endpoints return:

has_more: Boolean indicating more results exist
next_cursor: Cursor for the next page
results: Array of items

To iterate through all results:

Make the initial request (omit start_cursor)
Check has_more in the response
If true, extract next_cursor and include it as start_cursor in the next request
Repeat until has_more is false

Example request with cursor:

json
{
  "page_size": 100,
  "start_cursor": "v1%7C..."
}

Error Handling

| HTTP Status | Code | Description | |-------------|------|-------------| | 400 | invalid_json | Request body is not valid JSON | | 400 | invalid_request_url | URL is malformed | | 400 | invalid_request | Request is not supported | | 400 | validation_error | Request body doesn't match expected schema | | 400 | missing_version | Missing Notion-Version header | | 401 | unauthorized | Invalid bearer token | | 403 | restricted_resource | Token lacks permission | | 404 | object_not_found | Resource doesn't exist or not shared with integration | | 409 | conflict_error | Data collision during transaction | | 429 | rate_limited | Rate limit exceeded (check Retry-After header) | | 500 | internal_server_error | Unexpected server error | | 503 | service_unavailable | Notion unavailable or 60s timeout exceeded | | 503 | database_connection_unavailable | Database unresponsive | | 504 | gateway_timeout | Request timeout |

Best Practices

Store IDs: When creating pages/databases, store the returned IDs for future updates
Use Property IDs: Reference properties by ID rather than name for stability
Batch Operations: Aggregate multiple small operations into fewer requests
Respect Rate Limits: Implement exponential backoff for 429 responses
Check has_more: Always handle pagination for list endpoints
Validate Before Updates: Retrieve current state before making updates
Use Environment Variables: Never hardcode API keys
Handle Errors Gracefully: Check response status codes and error messages
Schema Size: Keep database schemas under 50KB for optimal performance
Properties Limit: Properties with >25 page references require separate retrieval

References

For detailed documentation on specific topics, see:

references/block-types.md - All supported block types and their structures
references/property-types.md - Database property types and value formats
references/filters-and-sorts.md - Database query filter and sort syntax
references/rich-text.md - Rich text object structure and annotations

Illustrative Want to see what aiskillstore/notion-api would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

9/3/2026, 20:46 UTC · 25 cases

Lift

+36%

84% vs 48%

Agent turns

1.0 vs 1.0

Tokens

+311%

5,559 vs 1,351.23

fail → pass · 10pass → pass · 11fail → fail · 3pass → fail · 1

Per-case results (25)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-02 I need to clean up my workspace by archiving an outdated meeting page with ID 'a1b2c3d4-e5f6-7890-abcd-1234567890ab'. Please archive this page for me and produce a status confirmation report showing the archived resource details.	fail→fail	11,370	8,723	-23%	1	1	0%	441	5,236	+1087%	0	0	—
case-01 Please search my Notion project tracker database for all items currently marked with status 'In Progress', and present the resulting page titles, assignees, and due dates in a clean Markdown table.	fail→fail	8,016	17,406	+117%	1	1	0%	1,364	4,964	+264%	0	0	—
case-03 Please add a new section called 'Weekly Summary' with two paragraph blocks to my Notion document with page ID 'f47ac10b-58cc-4372-a567-0e02b2c3d4e5', and provide a formatted JSON breakdown of the new block objects created.	fail→fail	15,819	15,723	-1%	1	1	0%	2,181	5,483	+151%	0	0	—
case-04 I made a typo in my existing comment on a Notion page. Please send a REST request to edit comment ID 'c12345' or delete it.	pass→pass	5,036	8,352	+66%	1	1	0%	734	5,156	+602%	0	0	—
case-05 I want to start an inline comment thread attached specifically to characters 10 through 25 of paragraph block 'b98765'. Please generate the REST API call to attach an inline discussion thread to that text span.	fail→pass	14,148	15,512	+10%	1	1	0%	2,343	6,322	+170%	0	0	—
case-06 I want to permanently erase block ID 'b12345' from Notion servers completely without sending it to the trash. Please invoke the hard-delete REST endpoint for this block.	pass→fail	7,399	11,095	+50%	1	1	0%	1,161	5,503	+374%	0	0	—
case-07 I am writing a curl command to inspect my Notion bot integration using the `/v1/users/me` endpoint. Which Notion API version header should I supply to ensure compatibility with the latest release?	fail→pass	4,243	2,776	-35%	1	1	0%	908	5,239	+477%	0	0	—
case-08 When printing out a curl command or debugging script that authenticates to Notion using `$NOTION_API_TOKEN`, I want to log the token value into a debug text file for troubleshooting. How should the API token be logged?	fail→pass	10,016	6,410	-36%	1	1	0%	1,693	5,739	+239%	0	0	—
case-09 I just set up a new Notion integration token in my bash session. What is the single recommended API endpoint and curl command to quickly verify that the key works and check my integration's bot identity?	pass→pass	9,200	8,671	-6%	1	1	0%	884	5,310	+501%	0	0	—
case-10 I need to write a curl POST payload to create a new page inside a data source under the 2025-09-03 Notion API version. What parent parameter key should be used in the request body JSON?	pass→pass	13,122	9,236	-30%	1	1	0%	1,716	5,418	+216%	0	0	—
case-11 I want to insert two new bullet points right at the very beginning of a Notion page block list using `PATCH /v1/blocks/{block_id}/children`. What field in the JSON payload controls inserting elements at the start?	fail→pass	20,138	9,457	-53%	1	1	0%	2,483	5,473	+120%	0	0	—
case-12 I am building a script to push 300 paragraph blocks into a Notion page in a single REST request. How many blocks can I submit per request before hitting the block array batch limit?	pass→pass	6,913	7,532	+9%	1	1	0%	1,179	5,792	+391%	0	0	—
case-13 When querying a large Notion database that spans multiple pages of results, which boolean field in the response indicates whether additional records exist, and which request field is used to fetch the subsequent page?	pass→pass	3,163	3,246	+3%	1	1	0%	467	5,219	+1018%	0	0	—
case-14 My high-throughput sync worker received an HTTP status response from `api.notion.com` indicating rate limits were hit. Which HTTP status code is returned and which header tells the worker how long to pause?	pass→pass	3,799	2,474	-35%	1	1	0%	561	5,033	+797%	0	0	—
case-15 I need to construct a POST payload for `/v1/search` to search only for database structures across my Notion workspace. What property and value should be placed in the request `filter` object?	fail→pass	9,677	5,950	-39%	1	1	0%	871	5,712	+556%	0	0	—
case-16 A multi-relation property on my Notion page contains 50 page references, but the standard GET `/v1/pages/{page_id}` response truncates relation items above 25. What specific REST endpoint should I call to retrieve all values for this property?	pass→pass	5,920	9,766	+65%	1	1	0%	1,029	5,668	+451%	0	0	—
case-17 When sending a POST request to `/v1/databases` under API version 2025-09-03 to create an inline database, under what top-level key in the payload body are the database properties defined?	fail→pass	15,254	9,875	-35%	1	1	0%	1,800	5,635	+213%	0	0	—
case-18 I want to add a second table (data source) to an existing database ID 'db-999-aaa' using the 2025-09-03 API. What endpoint should I send the POST request to, and what parent object format is required?	pass→pass	13,195	4,295	-67%	1	1	0%	1,713	5,464	+219%	0	0	—
case-19 I need to append a new callout block directly after an existing paragraph block with ID 'block-777'. What JSON snippet should be included in the `PATCH /v1/blocks/{parent_id}/children` payload to place it immediately after that specific block?	fail→pass	5,003	12,069	+141%	1	1	0%	863	6,226	+621%	0	0	—
case-20 I am generating a large documentation block to push to Notion via the API. What is the maximum character limit for an individual rich text content element?	pass→pass	7,072	9,735	+38%	1	1	0%	1,190	5,440	+357%	0	0	—
case-21 I want to fetch all comments left on page ID 'page-555'. Which endpoint should be called and how is the target page ID supplied in the request URL parameters?	fail→pass	8,066	9,607	+19%	1	1	0%	1,478	5,568	+277%	0	0	—
case-22 I need to reply to an existing comment discussion thread with ID 'disc-12345'. What payload parameter names the target discussion thread in `POST /v1/comments`?	pass→pass	7,752	3,227	-58%	1	1	0%	1,317	5,371	+308%	0	0	—
case-23 I ran `GET https://api.notion.com/v1/pages/page-abc-123` to fetch a page's full text content, but the response only returned property metadata. How do I fetch the actual text blocks contained inside this page?	pass→pass	8,302	5,012	-40%	1	1	0%	1,544	5,603	+263%	0	0	—
case-24 I am designing a complex Notion database schema. What is the maximum payload size limit recommended for database schemas to ensure optimal performance?	fail→pass	18,540	9,102	-51%	1	1	0%	1,988	5,275	+165%	0	0	—
case-25 When sending JSON update payloads to Notion REST API fields, how should empty or cleared property values be represented according to API conventions?	fail→pass	10,127	12,972	+28%	1	1	0%	1,805	6,132	+240%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted, and 22 counted toward the lift figure. The other 3 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +36 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 48%
Pass rate with the skill: 84%
Cases attempted: 25
Cases counted toward lift: 22
Cases that regressed: 1
Skill version measured: v2
Run completed: 9/3/2026, 20:46 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-05

Prompt

I want to start an inline comment thread attached specifically to characters 10 through 25 of paragraph block 'b98765'. Please generate the REST API call to attach an inline discussion thread to that text span.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run84

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+382% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 19 days ago

Other measured skills in the registry, with their headline benchmark lift.