petstore
Skill5 starsChanged 2 months agoMITView on GitHub
Use when you need to update an existing pet or other petstore operations from the shell. Run 'petstore describe' first.
- Reads credentials
In this repository57 other files it gives its agents.
- adversarial-reviewSkill
- aesthetic-animaxxingSkill
- ai-search-optimizationSkill
- announceSkill
- audio-trackSkill
- blindspotSkill
- brave-wesSkill
- chrome-wesSkill
- clihubSkill
- dashclaw-governanceSkill
- deskclawSkill
- de-vibeSkill
- dispatch-blocksSkill
- epic-infographicsSkill
- fable-gptSkill
- frontend-verifySkill
- gsap-astroSkill
- gsap-coreSkill
- gsap-frameworksSkill
- gsap-nextjsSkill
- gsap-nuxtSkill
- gsap-performanceSkill
- gsap-pluginsSkill
- gsap-react-routerSkill
- gsap-reactSkill
- gsap-scrolltriggerSkill
- gsap-sveltekitSkill
- gsap-tanstack-routerSkill
- gsap-timelineSkill
- gsap-utilsSkill
- gsap-vanillaSkill
- harness-healthSkill
- iphoneSkill
- landing-page-cro-expertSkill
- launchSkill
- launch-videoSkill
- logo-revealSkill
- marketingSkill
- marketing-studioSkill
- meditateSkill
- moleresearchSkill
- og-assetsSkill
- phone-gotchasSkill
- phoneSkill
- preflightSkill
- product-demoSkill
- ship-itSkill
- shipSkill
- show-meSkill
- skillfindSkill
- social-clipSkill
- spec-probeSkill
- teamSkill
- tregSkill
- wes-voiceSkill
- wrapSkill
- xplainerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 43
If 'petstore' is not on PATH, run every command as: declick run petstore <verb> ...
- Very specific: line 44
Every verb: --json (default when piped) --fields a,b --limit N.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
petstore
Generated by declick from https://petstore3.swagger.io/api/v3/openapi.json. Deterministic, no screenshots, JSON by default when piped.
petstore (openapi) source: https://petstore3.swagger.io/api/v3/openapi.json base: https://petstore3.swagger.io/api/v3
update-pet Update an existing pet. [mutating]
add-pet Add a new pet to the store. [mutating]
find-pets-by-status Finds Pets by status.
find-pets-by-tags Finds Pets by tags.
get-pet-by-id <petId> Find pet by ID.
update-pet-with-form <petId> Updates a pet in the store with form data. [mutating]
delete-pet <petId> Deletes a pet. [mutating]
upload-file <petId> Uploads an image. [mutating]
get-inventory Returns pet inventories by status.
place-order Place an order for a pet. [mutating]
get-order-by-id <orderId> Find purchase order by ID.
delete-order <orderId> Delete purchase order by identifier. [mutating]
create-user Create user. [mutating]
create-users-with-list-input Creates list of users with given input array. [mutating]
login-user Logs user into the system.
logout-user Logs out current logged in user session.
get-user-by-name <username> Get user by user name.
update-user <username> Update user resource. [mutating]
delete-user <username> Delete user resource. [mutating]
common: --json --fields --limit --rows --where --dry-run --full exit: 0 ok 1 err 2 missing 3 blocked 4 auth
auth env: PETSTORE_PETSTORE_AUTH, PETSTORE_API_KEYExamples (replace UPPERCASE tokens with real values; 'declick describe petstore --verb <verb>' prints one verb's flags and what it returns):
petstore update-pet --name doggie --photoUrls PHOTOURLS --dry-run
petstore add-pet --name doggie --photoUrls PHOTOURLS --dry-run
petstore find-pets-by-status --status STATUSIf 'petstore' is not on PATH, run every command as: declick run petstore <verb> ... (same output, same exit codes).
Every verb: --json (default when piped) --fields a,b --limit N; mutating verbs accept --dry-run. Success: {"ok":true,"data":...,"meta":{"count":N,"truncated":false}}. Failure: {"ok":false,"error":"...","exit":N}.
Exit 2 means not found, 3 blocked by governance, 4 auth needed (then: declick auth petstore).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

