@keystrokehq/skills 0.0.1

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

@@ -0,0 +1,29 @@
+{
+  "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-credential-binding/references/cli.md

@@ -0,0 +1,85 @@
+# Credential CLI Cookbook
+
+Read this file when the user asks how to inspect or upload credentials through the Keystroke CLI.
+
+## List existing credentials
+
+```bash
+keystroke credentials --json
+keystroke credentials list --json
+keystroke credentials list --scope organization --json
+keystroke credentials list --scope user --json
+keystroke credentials list --credential-set-id <credential-set-id> --json
+```
+
+Use these when the user wants to see what has already been uploaded and at which scope.
+
+## Inspect workflow credential requirements
+
+```bash
+keystroke credentials requirements --path <workflow-directory> --json
+```
+
+Use this before upload when the user wants to know which credential sets and keys are required.
+
+## Upload an official integration
+
+```bash
+keystroke credentials upload --integration <public-id> --path <workflow-directory> --json
+```
+
+Use this when the credential set belongs to an official Keystroke integration such as Slack, GitHub, or Linear and the values are already available as `KEYSTROKE_*` env vars.
+
+Useful variants from the current surface:
+
+```bash
+keystroke credentials upload --integration slack --path <workflow-directory> --dry-run --json
+keystroke credentials upload --integration github --path <workflow-directory> --update --json
+```
+
+## Upload an explicit credential set
+
+```bash
+keystroke credentials upload --credential-set <credential-set-id> --keys KEY_ONE,KEY_TWO --scope user --json
+```
+
+With env:
+
+```bash
+KEYSTROKE_KEY_ONE=first-value KEYSTROKE_KEY_TWO=second-value \
+keystroke credentials upload --credential-set <credential-set-id> --keys KEY_ONE,KEY_TWO --scope user --json
+```
+
+Use this path when:
+
+- the user already knows the credential set id
+- the user wants to upload one credential set directly
+- the workflow path is not the best entry point
+
+## How the env mapping works
+
+If the CLI expects keys such as:
+
+- `API_KEY`
+- `ACCOUNT_ID`
+
+then the env vars should be:
+
+- `KEYSTROKE_API_KEY`
+- `KEYSTROKE_ACCOUNT_ID`
+
+Example:
+
+```bash
+KEYSTROKE_API_KEY=secret KEYSTROKE_ACCOUNT_ID=acct_123 \
+keystroke credentials upload --credential-set billingApi --keys API_KEY,ACCOUNT_ID --scope organization --json
+```
+
+## Gotchas
+
+- Use the tested command names above. Do not invent a separate `credentials add` flow.
+- `--credential-set` requires `--keys`.
+- `--integration` is the preferred path for official Keystroke integrations.
+- Uploading depends on discoverable built manifests when the CLI needs workflow requirements from the project path.
+- For env-backed uploads, match the required key names with `KEYSTROKE_<KEY>`.
+- Do not teach stale flags such as `--from-workflows` or `--no-verify`.