Log a CLI in with a browser/device-code flow (aws sso, gh, glab, gcloud, …) and save the result to the keychain so later commands can request it through execute.credentials.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Nothing captures logins for you. Every login runs in a fresh temporary home and is saved
to the keychain with the script shipped with this skill. Never log in against the real
$HOME, and never treat a token or config already in $HOME as a usable login: only a
keychain handle is.
Make a fresh directory and start the login as a background job with every config
location pointed into it. Copy in any config the CLI needs first (for AWS, the
[profile …]/[sso-session …] blocks in .aws/config); everything under that
directory becomes the saved login.
d=$(mktemp -d) && echo "$d"
in_d() { env HOME="$d" XDG_CONFIG_HOME="$d/.config" XDG_DATA_HOME="$d/.local/share" XDG_STATE_HOME="$d/.local/state" XDG_CACHE_HOME="$d/.cache" "$@"; }
in_d aws sso login --profile work --use-device-code --no-browser
in_d gh auth login --hostname github.com --git-protocol https --web
in_d glab auth login --hostname gitlab.com --web
in_d gcloud auth login --no-launch-browser
Use the CLI's device-code mode (AWS needs --use-device-code); a browser flow only
completes on the same machine.
Relay the verification URL and code from the job output. Answer any prompt with send_input. Watch the job; never stop it while the person is approving.
When it exits successfully, save the directory with the script under the absolute directory the skill read reported:
node <skill dir>/scripts/save-login.mjs aws "$d" --label "work (123456789012)"
The script uploads only the files under that directory, removes the directory, and prints the credential handle. It also removes a directory that holds no usable login. Never remove the directory yourself; if the save fails, run the script again. Saving the same service again replaces that entry in place: its id, handle, owner and grants stay the same.
Use the login only by naming the handle in credentials on execute or a background
start, including to check that it works. The files are staged in a private home for
that command or job, and refreshes the CLI writes are saved back when it ends.
Never print token files or paste their contents into the conversation. If the login fails or expires, start again from step 1 with a new directory.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress) accepts your token when the user you're talking to is an org admin and started this turn themselves. Use when an admin asks you to inspect or change anything org-wide or in another scope, or anyone asks whether they're an admin.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a real stealth browser from your shell — act on websites (order food, file an expense, pull data behind a login), with per-person persistent sign-ins via the provider's managed auth (Kernel, Anchor, or Browserbase — picked by which API key you have). Use for ACTING on a site; to just read a page, use curl/wget first. Requires managed model access and a keychain grant for the browser provider key; follow the missing-key steps below.
日本語の概要は準備中です。原文の説明を表示しています。
Sign a cloud provider's CLI in (AWS, Google Cloud, Azure, or another) with a device-code flow, then run that CLI as the requesting user. Covers checking the CLI is installed, the login that survives the browser round-trip, and the boundaries on cloud writes.
日本語の概要は準備中です。原文の説明を表示しています。
Show the app connection picker or setup widget when users ask to connect apps, reopen setup, or need an app that isn't connected yet. Use QM’s authenticated backend for app discovery, consent, and execution without exposing project keys.
日本語の概要は準備中です。原文の説明を表示しています。
Connect an administrator-enabled SaaS app for a user with a one-time OAuth consent link.
日本語の概要は準備中です。原文の説明を表示しています。
Define a Loop — a durable scaffold that works a queue of recurring tasks autonomously (Sentry issues, Front tickets, small perf PRs) with its outputs held for human review. Use when someone wants an agent to keep doing a kind of work on a schedule, rather than one-off. Walks the interview, runs one real item live before arming anything, then writes the playbook and creates the loop.
日本語の概要は準備中です。原文の説明を表示しています。