@keystrokehq/skills 0.0.3 → 0.0.6

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": []
-    }
-  ]
-}

package/keystroke-trigger-authoring/references/source-map.md

@@ -1,128 +0,0 @@
-# Trigger Feature Map
-
-Use only the public imports a user repo can rely on:
-
-```ts
-import {
-  cronTrigger,
-  pollingTrigger,
-  providerTrigger,
-  webhookTrigger,
-} from '@keystrokehq/core';
-import type {
-  BoundTrigger,
-  CallableTrigger,
-  ExecutionIdentityPolicy,
-  TriggerBindOptions,
-  TriggerEntry,
-  TriggerInstance,
-} from '@keystrokehq/core/types';
-```
-
-When a trigger explanation also needs to talk about workflow steps or agent tools, use the terminology from the other Keystroke skills:
-
-- `Step`, `Tool`, and `Operation` are aliases for the same `Operation` class
-- use the workflow skill for workflow-side operation guidance
-- use the agent skill for agent-side tool guidance
-
-## Common trigger fields
-
-- `name`
-- `description`
-- `enabled`
-- `credentialSets`
-- `executionIdentityPolicy`
-- `modeDefault`
-
-## Common trigger methods
-
-- `describe()`
-- `toManifest()`
-
-## `cronTrigger` fields
-
-- `input`
-- `payload`
-- `schedule`
-- `timezone`
-
-## `cronTrigger` instance properties
-
-- `.name`
-- `.payload`
-- `.schedule`
-- `.timezone`
-- `.toManifest()`
-- `.describe()`
-
-## `webhookTrigger` fields
-
-- `path`
-- `method`
-- `payload`
-- `verify`
-- `filter`
-- `idempotencyKey`
-- `response`
-
-## `webhookTrigger` instance methods
-
-- `.payload.parse(data)` — validate parsed body against the payload schema
-- `.verify?(request, ctx)` — raw request + credentials for authenticity checks
-- `.filter?(payload, request?)` — typed parsed body, optional raw request (no credentials)
-- `.idempotencyKey?(payload, request?)` — typed parsed body, optional raw request (no credentials)
-
-## `pollingTrigger` fields
-
-- `schedule`
-- `response`
-- `poll`
-- `filter`
-- `idempotencyKey`
-
-## `pollingTrigger` instance methods
-
-- `.poll(ctx)`
-- `.parseResponse(response)`
-- `.filter?(payload)` — typed parsed payload (no credentials)
-- `.idempotencyKey?(payload)` — typed parsed payload (no credentials)
-
-## `providerTrigger` fields
-
-- `provider`
-- `eventTypes`
-- `appRef`
-- `filter`
-- `idempotencyKey`
-
-## Calling a trigger (creating a bound trigger)
-
-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
-
-## `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
-
-`Workflow({ triggers: [...] })` accepts a `TriggerEntry[]`:
-- a bare `CallableTrigger` (trigger payload passes through as workflow input)
-- a `BoundTrigger` (returned by calling the trigger with options)
-
-## Task note
-
-- task triggers are declared inline in `Task.triggers`
-- messaging gateways belong to agent authoring, not trigger authoring
-
-## Where to read next
-
-- `patterns.md` for trigger field examples
-- `testing.md` for trigger callback and bound trigger tests

package/keystroke-workflow-as-tool-debugging/evals/evals.json

@@ -1,23 +0,0 @@
-{
-  "skill_name": "keystroke-workflow-as-tool-debugging",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "A workflow tool with ctx.wait returned pending: true and the agent tried to call it again. What should I inspect and what behavior is expected?",
-      "expected_output": "Explains yield receipt behavior, turn ending, idempotency, pending yield state, child workflow run, and agent_continue resume path.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "My midSessionSnapshot workflow tool is suspended_snapshotted. When the child workflow completes, which worker should resume it?",
-      "expected_output": "States that agent_resume handles current snapshots through Path B conversation-log replay and does not claim native Pi process restore.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "A workflow tool returned a ref and the model wants to query it with a reducer. What should I do?",
-      "expected_output": "Recommends describe_ref/read_ref/slice_ref with bounded ranges and states reducers/DuckDB are deferred and unsupported.",
-      "files": []
-    }
-  ]
-}

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

@@ -1,29 +0,0 @@
-{
-  "skill_name": "keystroke-workflow-authoring",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I'm building a Keystroke workflow that checks a few upstream APIs, waits 10 minutes between retries, and then posts the result to Slack. Can you show me how to structure the workflow and what should be steps versus workflow orchestration?",
-      "expected_output": "Explains workflow planning, step boundaries, replay-safe orchestration, the durable wait path, and where Slack or other external work belongs.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "I have a workflow that uses Math.random() and Date.now() inside Workflow.run to make request ids. Why is that a problem in Keystroke, and how should I rewrite it?",
-      "expected_output": "Explains workflow replay safety, why nondeterministic logic should not live in the workflow body, and how to move it into a step or agent boundary.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "How do I test a Keystroke workflow that uses workflowGlobals and a webhook trigger? I want the recommended testing path, not a random custom harness.",
-      "expected_output": "Uses core Vitest helpers, covers workflowGlobals, and points to bound trigger transform testing via bound.transform?.(payload, ctx).",
-      "files": []
-    },
-    {
-      "id": 4,
-      "prompt": "Can my Keystroke workflow run bash to call a Python script, or should I structure this differently?",
-      "expected_output": "Explains that workflows are authored as TypeScript orchestration and do not run bash as part of the workflow model, then routes shell-heavy work to an agent sandbox.",
-      "files": []
-    }
-  ]
-}