--- name: store-ref-image description: Discover and invoke the STORE_REF_IMAGE directory capability using its live contract. Use when a request maps to this exact capability. --- # STORE_REF_IMAGE This Skill is the behavioral expression of [the STORE_REF_IMAGE directory article](/a/directory/STORE_REF_IMAGE). The directory row remains the executable contract. ## Operate 1. Read GET /api/directory/STORE_REF_IMAGE immediately before use. 2. Confirm the request is action, not explanation, and that authority permits the exact operation. 3. Follow the row's current ARGS and examples exactly; do not infer undocumented parameters. 4. Invoke POST /api/dispatch with {"key":"STORE_REF_IMAGE","body":""}. 5. Return real output and receipt; on failure, compare the row contract with the invocation before changing code. ## Human explanation # WHAT: Save a reference image (e.g. one sent via Blooio) to R2 and return {filename,key,url}. Arg: source_url # WHEN_TO_USE: you need to store ref image # ARGS: $1 # EX: [STORE_REF_IMAGE]arg1[/STORE_REF_IMAGE] ["$1"] ## Call it Every spelling below is the same call, with this row's own example arguments. `$TERMINAL_KEY` and `$MCP_TOKEN` are the owner's vault variables. Every spelling, with Run: https://miscsubjects.com/console#/api/STORE_REF_IMAGE ### HTTP · curl — the canonical call Any terminal or script. {key, body}: the arguments are one string, pipe-separated in the order below. The answer is {ok, ran, result, trace_id, receipt}. ```bash curl -sS -X POST 'https://ops.miscsubjects.com/api/dispatch' \ -H "x-terminal-key: $TERMINAL_KEY" \ -H 'content-type: application/json' \ --data '{"key":"STORE_REF_IMAGE","body":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}' ``` ### HTTP · curl — named arguments The same door with arguments by name: dispatch puts them in the row's order. Add "idempotency_key":"…" to make a retry safe (72 hours), "shape":true to see the request without sending it. ```bash curl -sS -X POST 'https://ops.miscsubjects.com/api/dispatch' \ -H "x-terminal-key: $TERMINAL_KEY" \ -H 'content-type: application/json' \ --data '{"key":"STORE_REF_IMAGE","args":{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}}' ``` ### HTTP · One URL — Safari, a Shortcut, any fetch tool A GET that runs the call from one address. The address holds a link scoped to this row that expires (ttl in seconds, uses= to cap the count) — never the master key. https://miscsubjects.com/web/run/STORE_REF_IMAGE?body=…&share=… is the same call for a browser model. Run mints a one-use link for itself. ``` # 1. a link that runs only STORE_REF_IMAGE, for an hour (share_token in the answer): curl -sS 'https://ops.miscsubjects.com/api/dispatch?mint_share=1&scope=row:STORE_REF_IMAGE&ttl=3600' \ -H "x-terminal-key: $TERMINAL_KEY" # 2. the address — paste it in Safari, a Shortcut or a model's fetch tool: https://ops.miscsubjects.com/api/dispatch?invoke=STORE_REF_IMAGE&body=https%3A%2F%2Fmiscsubjects.com%2Fimg%2Fref%2Fleo-vial-black-bg.png&share= ``` ### MCP · MCP over HTTP — misc_run The build's MCP server. misc_run reaches every row by key and leaves a receipt; misc_find finds the key from a phrase. The answer is result.content[0].text. ```bash curl -sS -X POST 'https://ops.miscsubjects.com/api/mcp' \ -H 'accept: application/json, text/event-stream' \ -H "authorization: Bearer $MCP_TOKEN" \ -H 'content-type: application/json' \ --data '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"misc_run","arguments":{"key":"STORE_REF_IMAGE","args":{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}}}}' ``` ### MCP · Claude Code Claude Code (terminal, desktop, web). The same server works in any Claude Code session once added. ``` # once, on any machine: claude mcp add --transport http miscsubjects https://ops.miscsubjects.com/api/mcp --header "Authorization: Bearer $MCP_TOKEN" # then in a session, the model calls: mcp__miscsubjects__misc_run {"key":"STORE_REF_IMAGE","args":{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}} ``` ### CLI · misc (on your Mac) The misc CLI in ~/.local/bin: its words go to /api/resolve (plan, then run), with TERMINAL_KEY from the vault. Arguments are positional, in the order above. `misc find "words"` finds a row. ```bash misc run STORE_REF_IMAGE https://miscsubjects.com/img/ref/leo-vial-black-bg.png misc store ref image https://miscsubjects.com/img/ref/leo-vial-black-bg.png ``` ### CLI · console-app The Console's own CLI. It reads the key from ~/.build-vault.env or `console-app login`. ```bash npm install -g https://miscsubjects.com/download/llmasos-console-1.1.0.tgz # once console-app call STORE_REF_IMAGE 'https://miscsubjects.com/img/ref/leo-vial-black-bg.png' console-app how STORE_REF_IMAGE # this page, in the terminal ``` ### CLI · One line of text — the build grammar /api/resolve parses the same line everywhere: "run KEY a b" (arguments in order, quoted when they hold spaces), the key's words ("store ref image …"), or a phrase it matches to a row. POST runs; {"run":false} returns the plan without running it. ``` # typed, texted to the build, or emitted by a model with no tools: run STORE_REF_IMAGE https://miscsubjects.com/img/ref/leo-vial-black-bg.png curl -sS -X POST 'https://ops.miscsubjects.com/api/resolve' \ -H "x-terminal-key: $TERMINAL_KEY" \ -H 'content-type: application/json' \ --data '{"line":"run STORE_REF_IMAGE https://miscsubjects.com/img/ref/leo-vial-black-bg.png","run":true}' ``` ### Agents · Tag form — inside an answer What a model in this build writes mid-answer to call a row; both tags always, even with nothing between them. {"emit": text} runs every tag in a piece of text and returns each result. ``` [STORE_REF_IMAGE]https://miscsubjects.com/img/ref/leo-vial-black-bg.png[/STORE_REF_IMAGE] # run text that carries tags, exactly as a model wrote it: curl -sS -X POST 'https://ops.miscsubjects.com/api/dispatch' \ -H "x-terminal-key: $TERMINAL_KEY" \ -H 'content-type: application/json' \ --data '{"emit":"[STORE_REF_IMAGE]https://miscsubjects.com/img/ref/leo-vial-black-bg.png[/STORE_REF_IMAGE]"}' ``` ### Phone · iPhone Shortcut — Get Contents of URL A Shortcut on the phone, a Siri phrase, an Action Button, or an automation. Swap body for Ask for Input to fill arguments at run time. ``` Action: Get Contents of URL URL: https://ops.miscsubjects.com/api/dispatch Method: POST Headers: x-terminal-key → (Text) your terminal key content-type → application/json Request Body: JSON key (Text) → STORE_REF_IMAGE body (Text) → https://miscsubjects.com/img/ref/leo-vial-black-bg.png Then: Get Dictionary Value result from Contents of URL ``` ### Webhook · A webhook any service can call Stripe, GitHub, Slack, Zapier, a form, a cron elsewhere. The hook id is the credential for an unsigned sender and it may run nothing but STORE_REF_IMAGE. mode "sync" answers with the result; "async" answers 202 at once. ``` # 1. once: make a hook that may run only STORE_REF_IMAGE (the answer holds its id and url) curl -sS -X POST 'https://ops.miscsubjects.com/api/hooks' \ -H "x-terminal-key: $TERMINAL_KEY" \ -H 'content-type: application/json' \ --data '{"label":"STORE_REF_IMAGE webhook","source":"url","allow_keys":["STORE_REF_IMAGE"],"effects_max":"write","mode":"sync"}' # 2. then any service POSTs the arguments, by name, to that url: curl -sS -X POST 'https://ops.miscsubjects.com/hook//STORE_REF_IMAGE' \ -H 'content-type: application/json' \ --data '{"arg1":"https://miscsubjects.com/img/ref/leo-vial-black-bg.png"}' ``` ### Upstream · What runs it Runs inside the build's own Worker as storeRefImage. It has no outside door of its own; every spelling above reaches it. ``` Runs inside the build's own Worker as storeRefImage. It has no outside door of its own; every spelling above reaches it. ```