@keystrokehq/skills 0.0.2 → 0.0.4

package/{keystroke-trigger-authoring → src/keystroke-trigger-authoring}/references/source-map.md

@@ -101,14 +101,13 @@ All factory-created triggers are callable. Calling one returns a `BoundTrigger`:
 
 - `trigger()` — bare binding (no transform)
 - `trigger({ transform })` — bound with payload-to-input mapping
-- `trigger({ filter })` — bound with additional filter
-- `trigger({ transform, filter })` — bound with both
+
+Bindings carry only `transform`. To filter events for a specific workflow, derive a child with `trigger.narrow({ name, filter })` and attach that — `.narrow()` is the only authoring path for per-target filtering. Binding-level `filter` and `idempotencyKey` are intentionally not part of the API.
 
 ## `BoundTrigger`
 
 - `.isBoundTrigger` — always `true`
 - `.trigger` — reference to the underlying trigger instance
-- `.filter?` — composed filter (trigger's filter + binding filter)
 - `.transform?` — payload-to-workflow-input mapping function
 
 ## Workflow `triggers` array

package/{keystroke-trigger-authoring → src/keystroke-trigger-authoring}/references/testing.md

@@ -6,11 +6,11 @@ Assume `paymentWebhook`, `orderPolling`, and `paymentWorkflow` are the public tr
 
 ## Vitest setup
 
-`keystrokeTestPlugin()` adds the core test setup file to Vitest, which is required for credential resolution and context mocking.
+`keystrokeTestPlugin()` adds the Keystroke testing setup file to Vitest, which is required for credential resolution and context mocking.
 
 ```ts
 import { defineConfig } from 'vitest/config';
-import { keystrokeTestPlugin } from '@keystrokehq/core/vitest';
+import { keystrokeTestPlugin } from '@keystrokehq/testing';
 
 export default defineConfig({
   plugins: [keystrokeTestPlugin()],

package/{keystroke-workflow-authoring → src/keystroke-workflow-authoring}/SKILL.md

@@ -123,7 +123,7 @@ Teach these rules:
    - waits and hooks
 5. Put operational work in steps, shared operations, or agents.
 6. Keep each exported primitive in its own typed file.
-7. Finish with tests using `@keystrokehq/core/vitest`.
+7. Finish with tests using `@keystrokehq/testing`.
 
 ## Workflow rules
 
@@ -202,7 +202,7 @@ keystroke workflows run <authoredWorkflowId> --input '{}' --wait
 keystroke workflows run <authoredWorkflowId> --input '{}' --follow
 ```
 
-`workflows run` executes the current deployed snapshot. It is different from `workflows try-deploy`, which builds local code and runs a temporary artifact.
+`workflows run` executes the current deployed snapshot. It is different from `workflows test`, which builds local code and runs a temporary artifact.
 
 To explicitly start a workflow via API:
 - **Endpoint**: `POST /api/v1/workflows/execute`

package/{keystroke-workflow-authoring → src/keystroke-workflow-authoring}/references/prebuilt-integrations.md

@@ -15,13 +15,13 @@ Use this rule:
 Install the package that exports the operation:
 
 ```sh
-pnpm add @keystroke/integration-slack
+pnpm add @keystrokehq/slack
 ```
 
 Import the named operation you want:
 
 ```ts
-import { sendMessage } from '@keystroke/integration-slack/platform/messages';
+import { sendMessage } from '@keystrokehq/slack/platform/messages';
 ```
 
 Call the operation directly from your workflow:
@@ -35,18 +35,18 @@ const result = await sendMessage.run({
 
 Replace `sendMessage` with any of the operation exports listed below.
 
-## `@keystroke/integration-ai`
+## `@keystrokehq/ai`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-ai
+pnpm add @keystrokehq/ai
 ```
 
 Import and use:
 
 ```ts
-import { generateObject, generateText } from '@keystroke/integration-ai/generate';
+import { generateObject, generateText } from '@keystrokehq/ai/generate';
 
 const summary = await generateText.run(/* AI text-generation input */);
 const structured = await generateObject.run(/* AI object-generation input */);
@@ -60,21 +60,21 @@ Also note:
 - this package exports AI provider credential sets for agent authoring
 - this package also exports generation operations, but agent authoring guidance belongs in the agent skill
 
-## `@keystroke/integration-apollo`
+## `@keystrokehq/apollo`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-apollo
+pnpm add @keystrokehq/apollo
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-apollo/accounts` or `@keystroke/integration-apollo/contacts`.
+Prefer domain subpath imports such as `@keystrokehq/apollo/accounts` or `@keystrokehq/apollo/contacts`.
 
 Import and use:
 
 ```ts
-import { createAccount } from '@keystroke/integration-apollo/accounts';
-import { searchContacts } from '@keystroke/integration-apollo/contacts';
+import { createAccount } from '@keystrokehq/apollo/accounts';
+import { searchContacts } from '@keystrokehq/apollo/contacts';
 
 const account = await createAccount.run(/* Apollo create-account input */);
 const contacts = await searchContacts.run(/* Apollo search-contacts input */);
@@ -128,20 +128,20 @@ const contacts = await searchContacts.run(/* Apollo search-contacts input */);
 - `createTasks`: Create Apollo tasks.
 - `searchTasks`: Search Apollo tasks.
 
-## `@keystroke/integration-attio`
+## `@keystrokehq/attio`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-attio
+pnpm add @keystrokehq/attio
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-attio/records` or `@keystroke/integration-attio/lists`.
+Prefer domain subpath imports such as `@keystrokehq/attio/records` or `@keystrokehq/attio/lists`.
 
 Import and use:
 
 ```ts
-import { createRecord, queryRecords } from '@keystroke/integration-attio/records';
+import { createRecord, queryRecords } from '@keystrokehq/attio/records';
 
 const record = await createRecord.run(/* Attio create-record input */);
 const records = await queryRecords.run(/* Attio query-records input */);
@@ -187,18 +187,18 @@ const records = await queryRecords.run(/* Attio query-records input */);
 - `listTasks`: List Attio tasks.
 - `updateTask`: Update an Attio task.
 
-## `@keystroke/integration-daytona`
+## `@keystrokehq/daytona`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-daytona
+pnpm add @keystrokehq/daytona
 ```
 
 Import example:
 
 ```ts
-import { DaytonaSandbox } from '@keystroke/integration-daytona';
+import { DaytonaSandbox } from '@keystrokehq/daytona';
 ```
 
 This package does not currently export workflow operations.
@@ -209,21 +209,21 @@ It currently exports sandbox utilities instead:
 - `DaytonaSandbox`: Create a Daytona-backed sandbox for agents.
 - `DaytonaSandboxProvider`: Configure the Daytona sandbox provider.
 
-## `@keystroke/integration-github`
+## `@keystrokehq/github`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-github
+pnpm add @keystrokehq/github
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-github/issues`, `@keystroke/integration-github/pull-requests`, or `@keystroke/integration-github/repos`.
+Prefer domain subpath imports such as `@keystrokehq/github/issues`, `@keystrokehq/github/pull-requests`, or `@keystrokehq/github/repos`.
 
 Import and use:
 
 ```ts
-import { getIssue } from '@keystroke/integration-github/issues';
-import { listPullRequests } from '@keystroke/integration-github/pull-requests';
+import { getIssue } from '@keystrokehq/github/issues';
+import { listPullRequests } from '@keystrokehq/github/pull-requests';
 
 const issue = await getIssue.run({
   owner: 'keystroke',
@@ -251,22 +251,22 @@ Common operation groups:
 
 Messaging-specific credential surfaces also exist in this package, but workflow trigger and conversation entry guidance belongs in the trigger and agent skills.
 
-## `@keystroke/integration-google`
+## `@keystrokehq/google`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-google
+pnpm add @keystrokehq/google
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-google/gmail`, `@keystroke/integration-google/sheets`, or `@keystroke/integration-google/calendar`.
+Prefer domain subpath imports such as `@keystrokehq/google/gmail`, `@keystrokehq/google/sheets`, or `@keystrokehq/google/calendar`.
 
 Import and use:
 
 ```ts
-import { listCalendarEvents, createCalendarEvent } from '@keystroke/integration-google/calendar';
-import { listEmails, sendEmail } from '@keystroke/integration-google/gmail';
-import { createSpreadsheet, writeSpreadsheetRange } from '@keystroke/integration-google/sheets';
+import { listCalendarEvents, createCalendarEvent } from '@keystrokehq/google/calendar';
+import { listEmails, sendEmail } from '@keystrokehq/google/gmail';
+import { createSpreadsheet, writeSpreadsheetRange } from '@keystrokehq/google/sheets';
 
 const inbox = await listEmails.run({
   labelIds: ['INBOX', 'UNREAD'],
@@ -332,23 +332,23 @@ await writeSpreadsheetRange.run({
 
 This package also exports agent-tool variants (`sendEmailTool`, `getEmailTool`, `listEmailsTool`, `labelEmailTool`, `createSpreadsheetTool`, `addSpreadsheetTabTool`, `readSpreadsheetTabTool`, `writeSpreadsheetRangeTool`, `listCalendarsTool`, `listCalendarEventsTool`, `getCalendarEventTool`, `createCalendarEventTool`, `updateCalendarEventTool`, `deleteCalendarEventTool`). Those are for agent authoring, not workflow steps.
 
-## `@keystroke/integration-hubspot`
+## `@keystrokehq/hubspot`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-hubspot
+pnpm add @keystrokehq/hubspot
 ```
 
-Prefer explicit subpaths such as `@keystroke/integration-hubspot/connection`,
-`@keystroke/integration-hubspot/triggers`, and domain paths like
-`@keystroke/integration-hubspot/companies` or `@keystroke/integration-hubspot/contacts`.
+Prefer explicit subpaths such as `@keystrokehq/hubspot/connection`,
+`@keystrokehq/hubspot/triggers`, and domain paths like
+`@keystrokehq/hubspot/companies` or `@keystrokehq/hubspot/contacts`.
 
 Import and use:
 
 ```ts
-import { createCompany } from '@keystroke/integration-hubspot/companies';
-import { searchContacts } from '@keystroke/integration-hubspot/contacts';
+import { createCompany } from '@keystrokehq/hubspot/companies';
+import { searchContacts } from '@keystrokehq/hubspot/contacts';
 
 const company = await createCompany.run(/* HubSpot create-company input */);
 const contacts = await searchContacts.run(/* HubSpot search-contacts input */);
@@ -390,21 +390,21 @@ const contacts = await searchContacts.run(/* HubSpot search-contacts input */);
 - `searchTickets`: Search HubSpot tickets.
 - `updateTicket`: Update a HubSpot ticket.
 
-## `@keystroke/integration-kalshi`
+## `@keystrokehq/kalshi`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-kalshi
+pnpm add @keystrokehq/kalshi
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-kalshi/markets` or `@keystroke/integration-kalshi/portfolio`.
+Prefer domain subpath imports such as `@keystrokehq/kalshi/markets` or `@keystrokehq/kalshi/portfolio`.
 
 Import and use:
 
 ```ts
-import { getMarkets } from '@keystroke/integration-kalshi/markets';
-import { createOrder } from '@keystroke/integration-kalshi/portfolio';
+import { getMarkets } from '@keystrokehq/kalshi/markets';
+import { createOrder } from '@keystrokehq/kalshi/portfolio';
 
 const markets = await getMarkets.run(/* Kalshi market-list input */);
 const order = await createOrder.run(/* Kalshi create-order input */);
@@ -542,20 +542,20 @@ const order = await createOrder.run(/* Kalshi create-order input */);
 
 This package also exports trigger helpers such as `polling`, `marketTrades`, `marketCandles`, `portfolioFills`, `portfolioOrderUpdates`, and `settledPositions`.
 
-## `@keystroke/integration-linear`
+## `@keystrokehq/linear`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-linear
+pnpm add @keystrokehq/linear
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-linear/issues` or `@keystroke/integration-linear/users`.
+Prefer domain subpath imports such as `@keystrokehq/linear/issues` or `@keystrokehq/linear/users`.
 
 Import and use:
 
 ```ts
-import { createIssue, searchIssues } from '@keystroke/integration-linear/issues';
+import { createIssue, searchIssues } from '@keystrokehq/linear/issues';
 
 const issue = await createIssue.run(/* Linear create-issue input */);
 const matches = await searchIssues.run(/* Linear search-issues input */);
@@ -616,22 +616,22 @@ const matches = await searchIssues.run(/* Linear search-issues input */);
 - `deleteWebhook`: Delete a Linear webhook.
 - `listWebhooks`: List Linear webhooks.
 
-## `@keystroke/integration-perplexity`
+## `@keystrokehq/perplexity`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-perplexity
+pnpm add @keystrokehq/perplexity
 ```
 
-Prefer subpath imports such as `@keystroke/integration-perplexity/search`, `@keystroke/integration-perplexity/stream`, and `@keystroke/integration-perplexity/generate`.
+Prefer subpath imports such as `@keystrokehq/perplexity/search`, `@keystrokehq/perplexity/stream`, and `@keystrokehq/perplexity/generate`.
 
 Import and use:
 
 ```ts
-import { generateText } from '@keystroke/integration-perplexity/generate';
-import { research, search } from '@keystroke/integration-perplexity/search';
-import { streamSearch } from '@keystroke/integration-perplexity/stream';
+import { generateText } from '@keystrokehq/perplexity/generate';
+import { research, search } from '@keystrokehq/perplexity/search';
+import { streamSearch } from '@keystrokehq/perplexity/stream';
 
 const answer = await generateText.run(/* Perplexity text-generation input */);
 const results = await search.run(/* Perplexity search input */);
@@ -642,21 +642,21 @@ const results = await search.run(/* Perplexity search input */);
 - `search`: Run a Perplexity search query.
 - `streamSearch`: Stream Perplexity search results.
 
-## `@keystroke/integration-polymarket`
+## `@keystrokehq/polymarket`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-polymarket
+pnpm add @keystrokehq/polymarket
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-polymarket/markets` or `@keystroke/integration-polymarket/discovery`.
+Prefer domain subpath imports such as `@keystrokehq/polymarket/markets` or `@keystrokehq/polymarket/discovery`.
 
 Import and use:
 
 ```ts
-import { getMarket } from '@keystroke/integration-polymarket/markets';
-import { search } from '@keystroke/integration-polymarket/discovery';
+import { getMarket } from '@keystrokehq/polymarket/markets';
+import { search } from '@keystrokehq/polymarket/discovery';
 
 const market = await getMarket.run(/* Polymarket get-market input */);
 const results = await search.run(/* Polymarket search input */);
@@ -709,21 +709,21 @@ const results = await search.run(/* Polymarket search input */);
 - `getPriceHistory`: Fetch historical price data for a market.
 - `listPrices`: List prices across markets.
 
-## `@keystroke/integration-scrapin`
+## `@keystrokehq/scrapin`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-scrapin
+pnpm add @keystrokehq/scrapin
 ```
 
-Prefer domain subpath imports such as `@keystroke/integration-scrapin/persons` or `@keystroke/integration-scrapin/companies`.
+Prefer domain subpath imports such as `@keystrokehq/scrapin/persons` or `@keystrokehq/scrapin/companies`.
 
 Import and use:
 
 ```ts
-import { getCompanyProfile } from '@keystroke/integration-scrapin/companies';
-import { searchPersons } from '@keystroke/integration-scrapin/persons';
+import { getCompanyProfile } from '@keystrokehq/scrapin/companies';
+import { searchPersons } from '@keystrokehq/scrapin/persons';
 
 const company = await getCompanyProfile.run(/* Scrapin company-profile input */);
 const people = await searchPersons.run(/* Scrapin search-persons input */);
@@ -760,21 +760,21 @@ const people = await searchPersons.run(/* Scrapin search-persons input */);
 - `resolvePersonByEmail`: Resolve a person from an email address.
 - `searchPersons`: Search people.
 
-## `@keystroke/integration-slack`
+## `@keystrokehq/slack`
 
 Install:
 
 ```sh
-pnpm add @keystroke/integration-slack
+pnpm add @keystrokehq/slack
 ```
 
-Prefer mode/domain imports such as `@keystroke/integration-slack/platform/messages` or `@keystroke/integration-slack/platform/users`.
+Prefer mode/domain imports such as `@keystrokehq/slack/platform/messages` or `@keystrokehq/slack/platform/users`.
 
 Import and use:
 
 ```ts
-import { sendMessage } from '@keystroke/integration-slack/platform/messages';
-import { listUsers } from '@keystroke/integration-slack/platform/users';
+import { sendMessage } from '@keystrokehq/slack/platform/messages';
+import { listUsers } from '@keystrokehq/slack/platform/users';
 
 const users = await listUsers.run(/* Slack list-users input */);
 const message = await sendMessage.run(/* Slack send-message input */);

package/{keystroke-workflow-authoring → src/keystroke-workflow-authoring}/references/runtime-helpers.md

@@ -239,7 +239,7 @@ Use these when operation behavior depends on retry state or when you want the st
 
 ## Public testing helpers
 
-Import these from `@keystrokehq/core/vitest`:
+Import these from `@keystrokehq/testing`:
 
 - `keystrokeTestPlugin`
 - `createTestRuntime`
@@ -248,7 +248,7 @@ Import these from `@keystrokehq/core/vitest`:
 
 ### What they are used for
 
-- `keystrokeTestPlugin`: Vitest plugin that wires core test setup into the test process
+- `keystrokeTestPlugin`: Vitest plugin that wires Keystroke testing setup into the test process
 - `createTestRuntime`: build a full workflow test runtime with workflow context plus step execution metadata
 - `createTestStepContext`: build only the operation / step context for isolated tests
 - `createMockHook`: create an immediately resolving hook for tests that would otherwise block on `ctx.createHook(...)`
@@ -256,7 +256,7 @@ Import these from `@keystrokehq/core/vitest`:
 Example:
 
 ```ts
-import { createMockHook } from '@keystrokehq/core/vitest';
+import { createMockHook } from '@keystrokehq/testing';
 
 const hook = createMockHook();
 await hook;

package/{keystroke-workflow-authoring → src/keystroke-workflow-authoring}/references/source-map.md

@@ -9,7 +9,7 @@ import {
   createTestRuntime,
   createTestStepContext,
   keystrokeTestPlugin,
-} from '@keystrokehq/core/vitest';
+} from '@keystrokehq/testing';
 ```
 
 `Operation`, `Step`, and `Tool` are aliases for the same class. In this workflow skill, prefer `Step` for examples and explanations, but `Operation` is equally valid for shared or integration-oriented code.

package/{keystroke-workflow-authoring → src/keystroke-workflow-authoring}/references/testing.md

@@ -6,11 +6,11 @@ Assume `helloWorkflow`, `accountSyncWorkflow`, `loadCustomer`, `paymentWebhook`,
 
 ## Vitest setup
 
-`keystrokeTestPlugin()` adds the core test setup file to Vitest. Use it when you want normal `workflow.run(...)` and `step.run(...)` calls to work in tests without building custom harness code first.
+`keystrokeTestPlugin()` adds the Keystroke testing setup file to Vitest. Use it when you want normal `workflow.run(...)` and `step.run(...)` calls to work in tests without building custom harness code first.
 
 ```ts
 import { defineConfig } from 'vitest/config';
-import { keystrokeTestPlugin } from '@keystrokehq/core/vitest';
+import { keystrokeTestPlugin } from '@keystrokehq/testing';
 
 export default defineConfig({
   plugins: [keystrokeTestPlugin()],
@@ -39,7 +39,8 @@ test('returns the greeting', async () => {
 Use it when a workflow test needs more than plain input data.
 
 ```ts
-import { createMockHook, createTestRuntime } from '@keystrokehq/core/vitest';
+import { createTestRuntime } from '@keystrokehq/testing';
+import { createMockHook } from '@keystrokehq/testing';
 
 const runtime = createTestRuntime({
   workflowGlobals: {
@@ -59,7 +60,7 @@ await accountSyncWorkflow.run(
 `createTestStepContext()` is the smaller helper for operation unit tests. Use it when you want to call `step.run(...)` or `operation.run(...)` directly and provide only the runtime context values that operation reads.
 
 ```ts
-import { createTestStepContext } from '@keystrokehq/core/vitest';
+import { createTestStepContext } from '@keystrokehq/testing';
 
 const stepContext = createTestStepContext({
   credentials: {

package/keystroke-agent-authoring/evals/evals.json

@@ -1,29 +0,0 @@
-{
-  "skill_name": "keystroke-agent-authoring",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I need a Keystroke agent that can look up Slack users and DM one of them. What fields should I set up, and where do tools and credentials go?",
-      "expected_output": "Explains the canonical Keystroke agent path, the important agent fields, tool configuration, and the credential relationship between the agent and its tools.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "Should this be a Step or an agent? The task is to inspect some repo files, decide what changed, and then call a couple of tools depending on what it finds.",
-      "expected_output": "Explains when an agent is appropriate, when a normal step would be better, and how workflow orchestration relates to agent scope.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "Show me how to build a sandboxed Keystroke coding agent that can work in a checked-out repo and maybe use MCP later if needed.",
-      "expected_output": "Uses the public sandbox and MCP patterns, points to MCP references when needed, and keeps workflow orchestration separate.",
-      "files": []
-    },
-    {
-      "id": 4,
-      "prompt": "I want my Keystroke agent to answer messages from GitHub conversations. Should I use a trigger or something else?",
-      "expected_output": "Explains that conversational entry belongs on Agent.messaging with a MessagingGateway, not on workflow triggers, and keeps the distinction between tasks, triggers, and conversations clear.",
-      "files": []
-    }
-  ]
-}

package/keystroke-cli-workspace/evals/evals.json

@@ -1,23 +0,0 @@
-{
-  "skill_name": "keystroke-cli-workspace",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I need to deploy a Keystroke task. What command should I use, and how should I inspect the available flags before running it?",
-      "expected_output": "Uses the CLI skill, chooses `keystroke deploy --target <task.task.ts>`, and tells the agent to inspect `keystroke deploy --help` first.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "How do I set up a new Keystroke project and make the Keystroke-authored skills available in Cursor?",
-      "expected_output": "Uses `keystroke init`, explains `keystroke skills sync`, and tells the agent to inspect command help first.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "I need to figure out which CLI options exist for uploading credentials. What should I do before running the upload command?",
-      "expected_output": "Explicitly uses `keystroke credentials upload --help` before describing the upload flow.",
-      "files": []
-    }
-  ]
-}

package/keystroke-credential-binding/evals/evals.json

@@ -1,29 +0,0 @@
-{
-  "skill_name": "keystroke-credential-binding",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I need to add a credential set for a new API integration in Keystroke. Can you show me how to define the CredentialSet and how a step would read it safely?",
-      "expected_output": "Explains CredentialSet authoring, typed schemas, and step context access through ctx.credentials.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "Before I deploy these workflows, how do I figure out which credentials are required and upload them from env vars with the Keystroke CLI?",
-      "expected_output": "Uses the tested credential requirements and upload flows, including the KEYSTROKE_<KEY> convention.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "Does the same credential model work for steps, tools, agents, and triggers, or are there important differences I need to know?",
-      "expected_output": "Explains the shared CredentialSet model and the differences in where credentials are attached and consumed across primitives.",
-      "files": []
-    },
-    {
-      "id": 4,
-      "prompt": "How do I upload official GitHub credentials with the current Keystroke CLI? Please use the real command surface, not an outdated one.",
-      "expected_output": "Uses the current credentials upload syntax, including --integration and the KEYSTROKE_<KEY> convention, and avoids stale flags such as --from-workflows or --no-verify.",
-      "files": []
-    }
-  ]
-}

package/keystroke-data-toolkit/evals/evals.json

@@ -1,23 +0,0 @@
-{
-  "skill_name": "keystroke-data-toolkit",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "My workflow tool can return a few megabytes of audit rows. How should I configure the workflow and how should the agent inspect the result?",
-      "expected_output": "Recommends largeResultMode: 'ref', explains the ref envelope, and uses describe_ref/read_ref/slice_ref with bounded ranges.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "The agent called read_ref and got truncated: true. What should it do next?",
-      "expected_output": "Explains that truncation is signaled and the agent should request a narrower range or targeted slice rather than assuming it saw all data.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "Can we add DuckDB reducers for this large CSV workflow output?",
-      "expected_output": "States that reducers and DuckDB are deferred in the active product and recommends bounded ref reads or samples instead.",
-      "files": []
-    }
-  ]
-}

package/keystroke-task-authoring/evals/evals.json

@@ -1,23 +0,0 @@
-{
-  "skill_name": "keystroke-task-authoring",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I want a Keystroke task that runs an agent every time a webhook fires and includes the webhook payload in the prompt. How should I author that?",
-      "expected_output": "Explains Task authoring, inline triggers, prompt templating with trigger context, and keeps workflow attachments out of the task path.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "Should this be a workflow or a task? The job is just: cron fires, agent writes a summary, then stop.",
-      "expected_output": "Chooses Task, explains why the task model fits better than workflow orchestration, and mentions deploy --target for focused task deploys.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "How do I limit a Keystroke task to run once and expire after a week?",
-      "expected_output": "Explains task lifecycle fields such as maxExecutions and expiresAfter with authored code examples.",
-      "files": []
-    }
-  ]
-}

package/keystroke-trigger-authoring/evals/evals.json

@@ -1,29 +0,0 @@
-{
-  "skill_name": "keystroke-trigger-authoring",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "How do I create a Keystroke webhook trigger for a Stripe event and map the incoming payload into my workflow input?",
-      "expected_output": "Explains webhookTrigger() factory setup, required and optional fields, and the bound trigger transform pattern via Workflow({ triggers: [trigger({ transform })] }).",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "I need a polling trigger that checks an external API every 15 minutes and only launches the workflow for new items. What should that look like?",
-      "expected_output": "Explains pollingTrigger() factory setup, schedule, poll/response, optional filter and idempotency behavior, and listing the trigger in Workflow({ triggers: [...] }) with optional transform binding.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "What is the right way to test a Keystroke trigger? I want to validate webhook verify/filter logic and the input transform into the workflow.",
-      "expected_output": "Points to trigger-specific callback tests (verify, filter, payload.parse) plus bound trigger transform testing via bound.transform?.(payload).",
-      "files": []
-    },
-    {
-      "id": 4,
-      "prompt": "I want a cron-driven agent job. Do I attach a trigger to the agent, attach it to a task, or something else?",
-      "expected_output": "Explains that workflow triggers are listed in Workflow({ triggers: [...] }), task triggers are listed inline on Task.triggers, and messaging gateways are not triggers.",
-      "files": []
-    }
-  ]
-}