Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/linear-performance-tuning
Optimize Linear API queries, caching, and batching for performance.
Passed 18 of 23 test cases with the skill, and 13 of 23 without it.
and 4 more in the full report
6 fixed12 passed either way4 still failing1 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.
Users report that workflow state dropdowns in our custom UI do not reflect updates made in Linear until hours later. What two strategy adjustments fix stale cache issues in a Linear integration?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends shortening the cache TTL | Missed | Passed |
| Recommends implementing webhook-driven cache invalidation | Passed | Passed |
The instructions your model reads when the skill loads.
Optimize Linear API usage for minimal latency and efficient resource consumption. The three main levers are: (1) query flattening to avoid N+1 and reduce complexity, (2) caching static data with webhook-driven invalidation, and (3) batching mutations into single GraphQL requests.
Key numbers:
firstupdatedAt to get fresh data first@linear/sdkThe SDK lazy-loads relations. Accessing .assignee on 50 issues makes 50 separate API calls.
import { LinearClient } from "@linear/sdk";
const client = new LinearClient({ apiKey: process.env.LINEAR_API_KEY! });
// BAD: N+1 — 1 query for issues + 50 for assignees + 50 for states = 101 requests
const issues = await client.issues({ first: 50 });
for (const i of issues.nodes) {
const assignee = await i.assignee; // API call!
const state = await i.state; // API call!
console.log(`${i.identifier}: ${assignee?.name} [${state?.name}]`);
}
// GOOD: 1 request — use rawRequest with exact field selection
const response = await client.client.rawRequest(`
query TeamDashboard($teamId: String!) {
test cases passed, vs 13 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.