@keystrokehq/cli 0.1.24 → 0.1.25

package/dist/skills-bundle/skills/keystroke-apps/references/cli-and-catalog.md

@@ -1,104 +0,0 @@
-# CLI, catalog, connect
-
-## Log in once
-
-```bash
-keystroke auth login
-keystroke auth status
-```
-
-Token is stored in the OS keychain and reused for all CLI commands. See [cli skill](.agents/skills/keystroke-cli/SKILL.md).
-
-## keystroke app commands
-
-All org-scoped; output is JSON.
-
-| Command | Purpose |
-| ------- | ------- |
-| `app list` | Apps registered/connectable in your org |
-| `app search <query>` | Search live Composio catalog (`--category`, `--limit`, `--cursor`) |
-| `app show <slug>` | Single catalog app details |
-| `app actions [slug]` | List actions for an app, or global search with `--search` (no slug) |
-| `app action <tool-slug>` | Full input/output JSON schema for one action |
-| `app create` | Create custom org app — manual (`--name`, `--slug`, `--description`, `--field`) or auto-detect (`--mcp`, `--openapi`, `--graphql`, `--preview`, `--auth`) |
-| `app sync <slug>` | Write `src/apps/<name>/app.ts` from platform template (`--dir`) |
-
-`--field` syntax: `key`, `key:secret`, `key:optional`, `key:public`, or combinations like `key:secret:optional` (repeatable). A bare `key` is **secret by default**; `:public` forces a non-secret field. Manual custom apps require at least one `--field`, and at least one of them must be required (not `:optional`).
-
-With `--mcp`, `--openapi`, or `--graphql`, auth and credential fields are auto-detected from the URL (same as the dashboard Create custom app dialog). Use `--preview` to print the assembled request without creating; override detected values with `--name`, `--slug`, `--description`, `--field`, or `--auth` (`oauth` / `api_key`, MCP only).
-
-```bash
-keystroke app create --mcp https://mcp.example.com/mcp --preview
-keystroke app create --openapi https://example.com/openapi.yaml --name "Example API"
-```
-
-## Connect an app
-
-`keystroke connect <slug>` attaches secrets to an app via the web app connect flow:
-
-```bash
-keystroke connect google          # official OAuth
-keystroke connect slack
-keystroke connect exa             # official API key
-keystroke connect acme/internal-api   # custom app (sync first)
-keystroke connect <slug> --print-url  # deeplink without opening browser
-```
-
-- **Official integrations** — always prefer `keystroke connect <slug>`
-- **Custom apps** — `keystroke app sync <slug>` first, then `keystroke connect <slug>`
-- Slug must exist in your org registry (`app list`)
-- The web app **Apps** page offers the same flow
-
-## Scopes
-
-A connection is stored at one scope. `keystroke connect` has **no** `--scope` flag — you choose the scope in the web connect flow. To set scope from the CLI, use `keystroke credentials set <key> --scope <scope> [--project-slug <slug>]` (that command defaults to `org`).
-
-| Scope | When |
-| ----- | ---- |
-| `project` | Tie to one project |
-| `org` | Share with every user and project |
-| `user` | Single user's personal connection |
-
-At runtime resolution prefers the **project default first, then the org default**. Get the active project id from `keystroke config show`.
-
-## Manage & bind credentials
-
-Day-to-day management (output is JSON):
-
-```bash
-keystroke credentials list                                   # every instance + scope + default flag
-keystroke credentials get <credential-id>
-keystroke credentials update <credential-id> --label "Prod" --default
-keystroke credentials rotate-key <credential-id> --set apiKey=@env:ACME_API_KEY
-keystroke credentials delete <credential-id>
-```
-
-`--default` marks one instance as the default for its app + scope. When several instances share a scope and none is the default, a run can't auto-resolve — set a default, or **bind** a specific instance to the step/tool that needs it.
-
-### Bind a specific instance to a step or tool
-
-An assignment pins an exact credential instance to one consumer. It's the **explicit selection** at the top of the resolution order, so it wins over scope defaults. List the bindable consumers first, then assign:
-
-```bash
-# Workflow consumers are step correlation ids from recent runs (step:<slug>#<n>)
-keystroke credentials consumers list --workflow sync
-keystroke credentials assignments assign --workflow sync --credential org/work --consumer step:fetch-gmail#0
-
-# Agent consumers are tool slugs
-keystroke credentials consumers list --agent support
-keystroke credentials assignments assign --agent support --credential vault-prod --consumer vault-lookup
-
-# Omit --consumer (or pass "*") to bind every consumer on the target
-keystroke credentials assignments assign --workflow sync --credential work
-
-keystroke credentials assignments list --workflow sync       # inspect bindings
-keystroke credentials assignments unassign <assignment-id>   # remove one
-```
-
-- Exactly one of `--workflow <slug>` or `--agent <slug>` is required.
-- `--credential` takes an instance slug: `work`, `org/work`, or `<app>/<slug>` (e.g. `linear/work`).
-- Workflow consumer ids only appear after a run has produced `step_completed` events; `consumers list` reads them from recent runs.
-
-## Where secrets live
-
-App secrets are **not** read from `.env` and are **never** uploaded by `keystroke deploy` — it ships code only. Attach integration secrets by connecting the app with `keystroke connect <slug>`; they're resolved at runtime for your project.

package/dist/skills-bundle/skills/keystroke-channels/SKILL.md

@@ -1,66 +0,0 @@
----
-name: keystroke-channels
-description: Let people use keystroke agents from Slack (external channels) — connect Slack, bind channels with `keystroke channel bind`, pick a listen mode. Use when setting up messaging for agents.
-metadata:
-  keystroke-domain: channels
----
-
-# External channels
-
-External channels route **Slack (and similar) messages** to an agent — people chat in-channel instead of using the CLI. Slack is the only channel today.
-
-## Setup (Slack)
-
-1. Deploy the agent you want to chat with (`keystroke deploy`)
-2. Connect Slack once for the org: `keystroke connect slack` (or the web app **Apps** page); complete OAuth
-3. Bind a channel to the agent (CLI below, or the agent's **External Channels** panel in the web app)
-4. Message the bound channel per its listen mode
-
-## Bind from the CLI
-
-```bash
-keystroke channel platforms list                                  # supported platforms
-keystroke channel accounts --platform slack                       # connected workspaces (team ids)
-keystroke channel directory --platform slack --account <team-id>  # channels you can bind
-keystroke channel bind \
-  --agent support \
-  --platform slack \
-  --account <team-id> \
-  --channel <channel-id> \
-  --mode mention
-keystroke channel list --agent support                            # bindings for an agent
-```
-
-Listen modes (`--mode`): `mention` (only when @mentioned), `all` (every message), `dm` (direct messages). Update or remove a binding with `keystroke channel update-binding --agent <id> --binding <id> --mode all` / `keystroke channel unbind --agent <id> --binding <id>`.
-
-`channel bind` also takes an optional `--channel-name <name>` (defaults to the channel id). Every `keystroke channel` subcommand accepts `--project <slug>` to target a non-active project; otherwise they use the active project.
-
-## What happens at runtime
-
-Inbound Slack event → lookup channel binding → `runPrompt` for the bound agent → reply in thread.
-
-The agent acts **on behalf of the channel**, not the sender: it runs with its own tools, actions, and credentials regardless of who messaged. Only bind agents to channels whose members you trust with everything the agent can do.
-
-## Audit channel-driven sessions
-
-The CLI session source is still named `gateway`:
-
-```bash
-keystroke agent sessions list <agent-key> --source gateway
-keystroke agent sessions get <agent-key> <session-id> --include messages,trace
-```
-
-## Troubleshooting
-
-| Issue       | Check                                                               |
-| ----------- | ------------------------------------------------------------------- |
-| Bot silent  | `keystroke agent sessions list` for errors; agent on the binding    |
-| "Choose an agent" prompt | The channel has no agent bound — bind one with `keystroke channel bind` |
-| OAuth fails | Slack redirect URLs match your project's web app origin             |
-| Wrong agent | Re-bind with `keystroke channel bind` (or the web app panel)        |
-
-## Next references
-
-- [slack-setup.md](references/slack-setup.md) — connect flow, testing against a deployed project
-
-Related: [agents](.agents/skills/keystroke-agents/SKILL.md), [apps](.agents/skills/keystroke-apps/SKILL.md).

package/dist/skills-bundle/skills/keystroke-channels/references/slack-setup.md

@@ -1,41 +0,0 @@
-# Slack channel setup
-
-## Connect Slack
-
-Connect the Slack app once for the org with `keystroke connect slack` — the Slack app credentials are entered in the web connect flow, not in your project's `.env`. The connected workspace stays connected; adding more agents is just a bind step.
-
-Slack OAuth and the inbound routes mount automatically on your **deployed** project, so connecting against the cloud target works out of the box — you don't add Slack to `keystroke.config.ts`.
-
-## Bind a channel
-
-```bash
-keystroke channel accounts --platform slack                       # find the team id
-keystroke channel directory --platform slack --account <team-id>  # find the channel id
-keystroke channel bind --agent support --platform slack \
-  --account <team-id> --channel <channel-id> --mode mention
-```
-
-`--mode` is `mention`, `all`, or `dm`. Thread follow-up is on by default; toggle it with `keystroke channel update-binding --agent <id> --binding <id> --threads` / `--no-threads`.
-
-The web app offers the same flow from each agent's **External Channels** panel.
-
-## Testing
-
-Slack OAuth and the inbound event routes are handled by your **deployed** project — `keystroke dev` (local watch/rebuild) is not in the Slack delivery path. To test Slack end-to-end: `keystroke deploy`, `keystroke connect slack`, `keystroke channel bind …`, then message the bound channel and inspect the session (below).
-
-> Self-hosting the keystroke platform is a separate concern: that setup seeds Slack app credentials via platform env vars (`SLACK_CLIENT_ID/SECRET/SIGNING_SECRET`) and a public origin (`PUBLIC_PLATFORM_PROXY_URL`). Those are **platform** vars, not part of a scaffolded user project, and `keystroke dev` does not read them.
-
-## Audit
-
-```bash
-keystroke agent sessions list <agent-key> --source gateway
-keystroke agent sessions get <agent-key> <session-id> --include messages,trace
-```
-
-## Common fixes
-
-| Issue         | Fix                                                |
-| ------------- | -------------------------------------------------- |
-| 401 on events | Check the signing secret in the Slack connection   |
-| No reply      | Session errors via `keystroke agent sessions list` |
-| Wrong agent   | Re-bind with `keystroke channel bind`              |

package/dist/skills-bundle/skills/keystroke-cli/SKILL.md

@@ -1,93 +0,0 @@
----
-name: keystroke-cli
-description: Keystroke CLI — log in, manage projects, deploy your src/, and run/inspect what's deployed (workflows, agents, triggers, apps). Use when running keystroke commands for a project.
-metadata:
-  keystroke-domain: cli
----
-
-# CLI
-
-The CLI is the primary interface for keystroke projects. You build in `src/`, deploy to your project on the platform, then run and inspect what's deployed. The loop is **edit → deploy → run/inspect → repeat**; deploy often.
-
-## Log in
-
-```bash
-keystroke auth login                 # once; token stored in the OS keychain and reused
-keystroke auth login --org <org-slug>  # headless org pick
-keystroke config org                 # list org memberships
-keystroke config use org <org-slug>  # switch active org
-```
-
-One login covers every command. `auth login` auto-picks your org if you have one and prompts if there are several.
-
-## Projects
-
-A **project** is your deploy target on the platform. `keystroke init` scaffolds the local repo; the platform project is where it runs.
-
-```bash
-keystroke project list
-keystroke project create --name "My app" --description "Optional"
-keystroke deploy --project <id>       # build + upload src/; see deploy skill for --filter
-```
-
-`--project` selects the deploy target. It's a global flag that works before or after the subcommand (`keystroke deploy --project <id>`).
-
-New projects are **inactive** until the first deploy. After a deploy, `keystroke deploy` remembers the project (saved in `~/.keystroke`), so later commands target it without `--project`. To switch which project later commands use:
-
-```bash
-keystroke config use project <id>
-```
-
-To target a different project for a single command without changing the default:
-
-```bash
-keystroke workflow runs list greeting --project <id>
-```
-
-By default the CLI targets the cloud platform. To run commands against a locally running server (`keystroke start` / `keystroke dev`), use the global `--local` flag for one command, or `keystroke config use local` / `keystroke config use cloud` to switch the default target.
-
-Full deploy, filtered module redeploy, and WIP ignore: [deploy skill](../keystroke-deploy/SKILL.md).
-
-## Pull an existing project
-
-`keystroke pull` is the inverse of `deploy`: it downloads a project's **active deploy source** into a local directory, installs dependencies, and syncs bundled skills. Use it to start working on a project that was created or deployed elsewhere (e.g. on a fresh machine).
-
-```bash
-keystroke pull --project <id>            # into the current directory
-keystroke pull --project <id> --dir ./my-app
-keystroke pull --project <id> --force    # overwrite an existing local tree
-```
-
-It targets the active project when `--project` is omitted. A directory that already holds an unrelated project is refused unless you pass `--force`; a directory from a prior pull of the **same** project refreshes in place, and a no-op pull (already on the active artifact) exits without changes.
-
-## Run & inspect
-
-After deploy, runtime commands operate on your project:
-
-```bash
-keystroke workflow run greeting --input '{"name":"Ada"}'
-keystroke workflow runs list greeting
-keystroke workflow runs get greeting <run-id> --include steps,trace
-keystroke agent prompt hello --message "Hi"
-keystroke agent sessions get support <session-id> --include messages,trace
-keystroke app list
-keystroke trigger list
-keystroke trigger list --endpoint stripe   # all webhooks on a shared endpoint
-keystroke trigger url stripe               # shared route URL (or a trigger key)
-```
-
-Always use the CLI to inspect runs and sessions — do not hand-craft HTTP requests.
-
-## Commands at a glance
-
-| Command                                            | What it does                                              |
-| -------------------------------------------------- | -------------------------------------------------------- |
-| `auth login`                                       | Authenticate; token reused for all commands              |
-| `project list`, `project create`                   | Manage deploy targets in the active org                  |
-| `deploy`                                           | Build `src/` and ship it; sets the active project        |
-| `pull`                                             | Download a project's active deploy source into a local dir |
-| `workflow`, `agent`, `trigger`, `app`              | Run and inspect resources on your project                |
-| `connect <slug>`                                   | Connect an integration (see apps skill)                  |
-| `config use project <id>`, `config show`           | Set/inspect the active project                           |
-
-Related: [deploy](../keystroke-deploy/SKILL.md), [apps](../keystroke-apps/SKILL.md), [workflows](../keystroke-workflows/SKILL.md), [agents](../keystroke-agents/SKILL.md), [triggers](../keystroke-triggers/SKILL.md).

package/dist/skills-bundle/skills/keystroke-deploy/SKILL.md

@@ -1,93 +0,0 @@
----
-name: keystroke-deploy
-description: Build and deploy keystroke projects — full deploy, filtered module redeploy, @keystroke ignore for WIP modules. Use when shipping to the platform or keeping draft code out of production.
-metadata:
-  keystroke-domain: deploy
----
-
-# Deploy
-
-Deploy uploads a `dist/` tarball to the keystroke **platform** and promotes a new project-server runtime (blue/green). Use this skill when shipping your project to the platform.
-
-## Prerequisites
-
-```bash
-keystroke auth login
-keystroke project list                    # or: project create --name "My app"
-keystroke deploy --project <slug>         # first deploy must be full (no --filter)
-```
-
-`--project` selects the deploy target; as a global flag it works before or after `deploy`. After a successful deploy the project becomes the active target (saved in `~/.keystroke`), so later commands (including subsequent deploys) can omit it.
-
-Deploy always **builds before upload**. Full deploy wipes `dist/` (`clean: true`), rebuilds all modules, regenerates `route-manifest.json`, then packs and uploads.
-
-## Full deploy
-
-```bash
-keystroke build                           # optional preview; deploy rebuilds anyway
-keystroke deploy --project <slug>
-keystroke deploy --project <slug> --dir ./my-app
-```
-
-After success the project becomes the active target for later commands. Verify with `keystroke workflow run <key> --input '{}'`.
-
-## Filtered deploy (one module)
-
-Redeploy a single agent/workflow/trigger without rebuilding everything. Requires an **active** artifact from a prior full deploy.
-
-```bash
-keystroke deploy --project <slug> --filter workflows/morning-check
-keystroke deploy --project <slug> --filter agents/support --filter workflows/signup-pipeline
-```
-
-`--filter` matches exact build entry keys (`agents/foo`, `workflows/bar`, `triggers/baz`) — the paths under `src/` without extension. Repeat the flag for multiple modules. No globs.
-
-**How it works:** isolated rebuild of each matched module → download active prod tarball → overlay rebuilt `.mjs` files → merge `route-manifest.json` by module → upload as a normal full deploy.
-
-**Carried forward from prod:** `config.mjs`, bundled assets, skills metadata, and all untouched modules. Skill/asset drift is not validated in v1.
-
-Detail: [filtered-deploy.md](references/filtered-deploy.md).
-
-## WIP modules (`@keystroke ignore`)
-
-Keep draft agents/workflows/triggers in `src/` but out of the runtime:
-
-```ts
-// @keystroke ignore          // skip local build, dev, and deploy
-// @keystroke ignore:deploy   // local build + dev only; omitted from deploy
-```
-
-- `ignore` — broken or not-ready; stays out of `dist/` everywhere.
-- `ignore:deploy` — runs locally; excluded from deploy only.
-
-Import guard: a shipped module that **imports** an `@keystroke ignore` file fails the build in **every** phase; importing an `@keystroke ignore:deploy` file builds fine locally and fails only at **deploy** time. Triggers attached to an ignored workflow need the same directive.
-
-Detail: [wip-ignore.md](references/wip-ignore.md).
-
-## Build vs deploy
-
-| Command            | Phase   | Output                                      |
-| ------------------ | ------- | ------------------------------------------- |
-| `keystroke build`  | `build` | `dist/` for inspection                      |
-| `keystroke deploy` | `deploy`| `dist/` + upload; honors `ignore:deploy`    |
-
-Deploy always runs a fresh, clean build before upload.
-
-Detail: [build-and-full-deploy.md](references/build-and-full-deploy.md).
-
-## Common mistakes
-
-- **First deploy with `--filter`** — fails; run full deploy once.
-- **Wrong `--dir`** — builds a different tree than you edited.
-- **Expecting full refresh with `--filter`** — only matched modules rebuild; rest comes from active prod.
-- **Connected apps aren't in `.env`** — deploy never uploads `.env`; connect apps for your project. See [apps skill](../keystroke-apps/SKILL.md).
-
-## Audit deployed runtime
-
-```bash
-keystroke project deployments list --project <slug>
-keystroke workflow run morning-check --input '{}'
-keystroke trigger list
-```
-
-Related: [cli skill](../keystroke-cli/SKILL.md), [apps skill](../keystroke-apps/SKILL.md).

package/dist/skills-bundle/skills/keystroke-deploy/references/build-and-full-deploy.md

@@ -1,30 +0,0 @@
-# Build and full deploy
-
-## What deploy does
-
-1. `walkProject` with `phase: "deploy"` — applies `@keystroke ignore:deploy`, collects source snapshot for the dashboard.
-2. `buildApp` — tsdown with `clean: true`; writes `dist/` and `dist/.keystroke/route-manifest.json`.
-3. `packProjectArtifact` — gzip tarball of `dist/`.
-4. Platform `artifacts.create` → PUT tarball → `complete` → blue/green promote.
-
-Source files upload in parallel (content-addressed); failure there warns but does not block deploy. The dashboard source snapshot is capped (per-file 256KB, total 8MB, 2000 files) and skips binaries, `.env`, and `.log` files — so `.env` is never uploaded.
-
-After upload, the CLI polls the project status (every ~2s, up to a 120s timeout) until it reports `active` or `failed`; on failure it surfaces the platform's `lastError`. A hang usually means the platform promotion is still in progress.
-
-## Entry keys
-
-Build entry keys mirror `dist/` paths without `.mjs`:
-
-| Source file                    | Entry key              |
-| ------------------------------ | ---------------------- |
-| `src/agents/support.ts`        | `agents/support`       |
-| `src/workflows/morning-check.ts` | `workflows/morning-check` |
-| `src/triggers/incoming-message.ts` | `triggers/incoming-message` |
-
-Nested agent dirs use the same `agents/<id>` pattern from discovery.
-
-## Freshness
-
-Full deploy always runs `buildApp` before pack. Default `clean: true` removes prior `dist/` output before rebuild. You do not need a separate `keystroke build` before deploy.
-
-Orphan files from removed modules are unlikely to affect routing — `route-manifest.json` is regenerated and drives HTTP routes.

package/dist/skills-bundle/skills/keystroke-deploy/references/filtered-deploy.md

@@ -1,50 +0,0 @@
-# Filtered deploy (`--filter`)
-
-Ship changes to one or a few modules without a full rebuild of every agent, workflow, and trigger.
-
-## Command
-
-```bash
-keystroke deploy --project <slug> --filter workflows/morning-check
-keystroke deploy --project <slug> --filter agents/support --filter workflows/signup-pipeline
-```
-
-(`--project` can go before or after `deploy`, and can be omitted after the first deploy.)
-
-- Exact entry keys only — no globs, no negation, no slug aliases.
-- First deploy for a project must be **full** (no `--filter`).
-- Without an active artifact, deploy errors: run a full deploy first.
-
-## Pipeline
-
-```text
-isolated single-entry build per --filter match (self-contained .mjs)
-  → download active prod tarball
-  → extract → overlay rebuilt files → merge route-manifest by moduleFile
-  → re-tar → normal artifacts.create / PUT / complete
-```
-
-## Isolated builds
-
-Each filtered module is built alone in a scratch dir. Output is self-contained (no shared `../chunk-*.mjs` imports). The merge overlays only `dist/<kind>/<id>.mjs` (+ `.map`) onto the extracted prod tree.
-
-## Manifest merge
-
-For each rebuilt module, base manifest entries with the same `moduleFile` are dropped; rebuilt entries are appended. Health, plugins, skills, integrations, and untouched modules stay from the active artifact.
-
-## What is not rebuilt
-
-- `config.mjs` and built-in integration routes
-- `dist/.keystroke/assets.mjs` and skill files on disk
-- Any module not listed in `--filter`
-
-Change `keystroke.config.ts` or project-wide assets → run a **full** deploy.
-
-## Verify
-
-```bash
-keystroke project deployments list --project <slug>   # new version active
-keystroke workflow run <workflow-slug> --input '{}'
-```
-
-Confirm untouched routes still work after a filtered deploy of a different module.

package/dist/skills-bundle/skills/keystroke-deploy/references/wip-ignore.md

@@ -1,35 +0,0 @@
-# WIP modules and `@keystroke ignore`
-
-Place the directive in the **leading comment block** of a module file under `src/agents/`, `src/workflows/`, or `src/triggers/` (the scan stops at the first non-comment line). Line (`//`) and block (`/* … */`, `*`) comments both work.
-
-```ts
-// @keystroke ignore
-// @keystroke ignore:deploy
-/** @keystroke ignore */
-```
-
-Only `ignore` and `ignore:deploy` are valid. Any other scope (e.g. `// @keystroke ignore:build`) throws `Unknown @keystroke ignore target "…"` at build time.
-
-## Directives
-
-| Directive              | Local build (`build`, `dev`, `start`) | Deploy (`phase: deploy`) |
-| ---------------------- | ------------------------------------- | ------------------------ |
-| `// @keystroke ignore` | Skipped                               | Skipped                  |
-| `// @keystroke ignore:deploy` | Included                      | Skipped                  |
-
-## When to use which
-
-- **`ignore`** — module is broken, experimental, or not ready to run anywhere.
-- **`ignore:deploy`** — safe to run locally; not ready for production yet.
-
-## Import guard
-
-If a **shipped** module imports a file marked `@keystroke ignore`, the build **fails in every phase**. If it imports an `@keystroke ignore:deploy` file, the local build/dev succeeds and only the **deploy** build fails (because `ignore:deploy` files are excluded only in the deploy phase). Compose in workflows instead of importing ignored actions from production modules.
-
-## Triggers
-
-A trigger attached to an ignored workflow should use the same ignore treatment, or the attachment will not behave as expected across build phases.
-
-## Filtered deploy note
-
-`ignore:deploy` omits a module from the **new** build. It does **not** keep the last prod version — full deploy replaces the entire artifact. Use filtered deploy when you want to update one live module while carrying forward the rest of prod.

package/dist/skills-bundle/skills/keystroke-files/SKILL.md

@@ -1,43 +0,0 @@
----
-name: keystroke-files
-description: Add static files to agent workspaces from src/files/ — product docs, instructions, context. Use with defineSandbox on defineAgent.
-metadata:
-  keystroke-domain: files
----
-
-# Files
-
-Files under `src/files/` mount into the agent sandbox at `/workspace/agent/`.
-
-## Layout
-
-```
-src/files/support/
-  product-guide.md
-  support-instructions.md
-  runbooks/
-    refunds.md
-```
-
-Nested directories are preserved — `src/files/support/runbooks/refunds.md` mounts at `/workspace/agent/runbooks/refunds.md`.
-
-```ts
-import { defineAgent } from "@keystrokehq/keystroke/agent";
-import { defineSandbox } from "@keystrokehq/keystroke/sandbox";
-
-export default defineAgent({
-  slug: "support",
-  systemPrompt: "Read /workspace/agent/product-guide.md before answering.",
-  sandbox: defineSandbox({ files: true }), // uses agent slug → src/files/support/
-});
-```
-
-Use `defineSandbox({ files: "shared" })` to mount `src/files/shared/` instead — the string value names the folder under `src/files/`.
-
-If the named folder doesn't exist, the build fails with a clear error — create the folder (it must contain at least one file) before deploying.
-
-Files are seeded **write-once** at sandbox startup: the agent can edit them at runtime, but those edits aren't persisted back to `src/files/` and reset on the next run. Treat `src/files/` as read-only seed content.
-
-Point the agent at paths in `systemPrompt`. After deploy, verify behavior with `keystroke agent prompt support --message "…"`.
-
-Related: [agents](.agents/skills/keystroke-agents/SKILL.md), [skills](.agents/skills/keystroke-skills/SKILL.md).

package/dist/skills-bundle/skills/keystroke-skills/SKILL.md

@@ -1,42 +0,0 @@
----
-name: keystroke-skills
-description: Add Agent Skills playbooks in src/skills/ for defineAgent — SKILL.md format, optional references. Use when giving agents domain-specific instructions.
-metadata:
-  keystroke-domain: skills
----
-
-# Project skills
-
-Skills are playbooks the agent loads on demand. Author in `src/skills/`, attach by folder name on the agent.
-
-## Layout
-
-```
-src/skills/support/
-  SKILL.md
-  references/refund-policy.md   # optional
-```
-
-```ts
-defineAgent({
-  slug: "support",
-  skills: ["support"] /* … */,
-});
-```
-
-At runtime → `/workspace/agent/skills/support/`.
-
-## SKILL.md
-
-Follow [Agent Skills](https://agentskills.io/specification): YAML frontmatter with `name` (matches the folder) and `description` are the required fields; everything else (e.g. `metadata`) is optional. Keep the body short; put detail in `references/`.
-
-## Two kinds of skills (don't confuse them)
-
-- **`src/skills/`** — *project* Agent Skills attached to your agents via `skills: [...]`. They deploy with your project; inspect deployed ones with `keystroke skill list`.
-- **`.agents/skills/`** — the *bundled coding-agent* guides (like this one) that `keystroke init` scaffolds. Refresh them to the current CLI version with `keystroke skills sync` (note the plural `skills`).
-
-## External registries
-
-Browse [skills.sh](https://skills.sh) — copy into `src/skills/{name}/` and fix `name` to match the folder.
-
-Related: [agents](.agents/skills/keystroke-agents/SKILL.md), [files](.agents/skills/keystroke-files/SKILL.md).