@keystrokehq/skills 0.0.2 → 0.0.4

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