starred/yaak-mountain-loop
1
0
Fork 0
mirror of https://github.com/mountain-loop/yaak.git synced 2026-09-10 20:01:55 +02:00
Code Issues 8 Packages Projects Releases 10 Wiki Activity

fix(cli): focus the agent skill description on when to use it (#625)

Browse Source
This commit is contained in:
Gregory Schier
2026-09-09 08:50:26 -07:00
committed by GitHub
parent d2d4b80a09
commit d5d2a64c32
1 changed files with 7 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
crates-cli/yaak-cli/skills/use-yaak/SKILL.md
+7 -14
View File
@@ -1,19 +1,12 @@
--- ---
name: use-yaak name: use-yaak
description: > description: >
Build and run HTTP API requests with the Yaak CLI (`yaak`): create workspaces, Use when the user mentions Yaak, a Yaak workspace, or the `yaak` command, or
folders, environments and variables, author HTTP requests, configure asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API
authentication (OAuth 2.0, bearer tokens, API keys, basic, JWT, AWS SigV4), requests for reuse or manual testing, configure auth on saved requests, import
send them individually or a whole folder/workspace at once, chain one an OpenAPI spec, a Postman or Insomnia collection, or a cURL command, or run
request's response into the next, and import existing APIs from OpenAPI, saved requests across environments. Prefer over one-off `curl` when requests
Postman, Insomnia, or cURL. Use this skill whenever the user mentions Yaak, a should be saved, reused, shared, or run as a set.
Yaak workspace, or the `yaak` command, and also when they ask to try, hit,
call, exercise, or smoke test an HTTP or REST endpoint, to save or organize
API requests for reuse, to set up API requests for manual testing, to add auth
to a saved request, to turn an OpenAPI or Postman collection into runnable
requests, or to run a saved request suite against staging versus production.
Prefer this over one-off `curl` commands whenever the requests should be
saved, reused, shared, or run as a set.
allowed-tools: Bash(yaak:*), Bash(which:*), Bash(command:*), Bash(npm:*), Bash(npx:*) allowed-tools: Bash(yaak:*), Bash(which:*), Bash(command:*), Bash(npm:*), Bash(npx:*)
--- ---
@@ -34,7 +27,7 @@ only for publishing plugins to the Yaak registry.
Two consequences worth holding onto. Requests you create are permanent user data Two consequences worth holding onto. Requests you create are permanent user data
in an app they use, not scratch files, so name them the way the user would and in an app they use, not scratch files, so name them the way the user would and
clean up anything created just to test. And because the app is right there, the clean up anything created just to test. And because the app is right there, the
CLI is usually the wrong place to *read* a response in detail; it is the right CLI is usually the wrong place to _read_ a response in detail; it is the right
place to build, organize, and run requests. place to build, organize, and run requests.
## The CLI describes itself ## The CLI describes itself