Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asgard-ai-platform/tech-api-integration
Guide REST API integration including HTTP methods, authentication, error handling, and rate limiting.
Passed 22 of 23 test cases with the skill, and 16 of 23 without it.
and 8 more in the full report
6 fixed16 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are starting a new integration with the Salesforce REST API. Our team wants to jump straight into coding feature logic and UI integration. What initial step must be completed before writing feature code or setting up error handling?
| Checked | Without skill | With skill |
|---|---|---|
| mandates reading API documentation completely before building features | Missed | Passed |
The instructions your model reads when the skill loads.
IRON LAW: Read the Docs, Then Build, Then Handle Errors
1. Read the API documentation completely (auth, endpoints, rate limits, errors)
2. Get a successful request working in isolation (curl/Postman)
3. Build error handling BEFORE building features
Skipping step 1 wastes hours on trial-and-error. Skipping step 3
creates fragile integrations that break silently in production.
| Method | Purpose | Idempotent? | Example |
|---|---|---|---|
| GET | Read data | Yes | GET /users/123 |
| POST | Create new resource | No | POST /users + body |
| PUT | Replace entire resource | Yes | PUT /users/123 + full body |
| PATCH | Update partial resource | Yes | PATCH /users/123 + partial body |
| DELETE | Remove resource | Yes | DELETE /users/123 |
| Range | Meaning | Common Codes |
|---|---|---|
| 2xx | Success | 200 OK, 201 Created, 204 No Content |
| 3xx | Redirect | 301 Moved, 304 Not Modified |
| 4xx | Client error (your fault) | 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 429 Too Many Requests |
| 5xx | Server error (their fault) | 500 Internal, 502 Bad Gateway, 503 Service Unavailable |
| Type | How It Works | When Used |
|---|---|---|
| API Key | Key in header or query param | Simple APIs, server-to-server |
| Bearer Token | Authorization: Bearer <token> | OAuth 2.0, JWT-based APIs |
test cases passed, vs 16 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.