Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/glean-core-workflow-a
Execute Glean primary workflow: search, chat, and AI-powered answers across enterprise data.
Passed 20 of 24 test cases with the skill, and 8 of 24 without it.
and 14 more in the full report
12 fixed8 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What HTTP method and endpoint base path prefix should be used for Glean Client API search, chat, and autocomplete requests?
| Checked | Without skill | With skill |
|---|---|---|
| The HTTP request method used across the endpoints is POST. | Passed | Passed |
| The endpoint path prefix used is /client/v1/. | Missed | Passed |
The instructions your model reads when the skill loads.
Build search and chat experiences using the Glean Client API. Covers full-text search with filters, AI-powered chat answers, and autocomplete suggestions.
const results = await fetch(`${GLEAN}/client/v1/search`, {
method: 'POST', headers: searchHeaders,
body: JSON.stringify({
query: 'kubernetes deployment best practices',
pageSize: 20,
requestOptions: {
datasourceFilter: 'confluence,github',
facetFilters: [{ fieldName: 'author', values: ['engineering-team'] }],
},
}),
}).then(r => r.json());
results.results?.forEach((r: any) => {
console.log(`[${r.datasource}] ${r.title}`);
console.log(` ${r.snippets?.[0]?.snippet ?? ''}`);
});
const chatResponse = await fetch(`${GLEAN}/client/v1/chat`, {
method: 'POST', headers: searchHeaders,
body: JSON.stringify({
messages: [{ role: 'USER', content: 'What is our deployment process for production?' }],
applicationId: 'my-app',
}),
}).then(r => r.json());
test cases passed, vs 8 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.