@usecoil/skill-claude 0.1.3 → 0.1.4

package/README.md

@@ -7,7 +7,7 @@ installed CLI and installs the compatible `@usecoil/cli` package when
 `coil` is not already available:
 
 ```bash
-npx --yes @usecoil/skill-claude@0.1.3 --base-url https://www.usecoil.com
+npx --yes @usecoil/skill-claude@0.1.4 --base-url https://www.usecoil.com
 coil config set-base-url https://www.usecoil.com --profile prod
 printf '%s' "$COIL_API_KEY" | coil auth login --profile prod --key -
 coil --profile prod agent-context --json

package/bin/install.mjs

@@ -307,12 +307,6 @@ function checkCli() {
       && fetchCount?.required === true
       && fetchCount?.minimum === 1
       && fetchCount?.maximum === 25;
-    const hasCommand = (group, name) => Array.isArray(context.commands?.[group]?.commands)
-      && context.commands[group].commands.some((command) => command?.name === name);
-    const hasLeadImport = hasCommand('leads', 'leads import');
-    const hasImportOutcomes = hasCommand('recipes', 'recipe-runs import-outcomes');
-    const hasImportedLeads = hasCommand('recipes', 'recipe-runs leads');
-    const hasNamedAgents = hasCommand('agents', 'agents list');
     const compatible = contextResult.status === 0
       && context.cli?.name === 'coil'
       && context.cli?.version === version.replace(/^v/, '')
@@ -320,11 +314,7 @@ function checkCli() {
       && hasSpendGate
       && hasStarterCap
       && Array.isArray(context.commands?.recipes?.commands)
-      && context.commands.recipes.commands.some((command) => command?.name === 'recipes run')
-      && hasLeadImport
-      && hasImportOutcomes
-      && hasImportedLeads
-      && hasNamedAgents;
+      && context.commands.recipes.commands.some((command) => command?.name === 'recipes run');
     return {
       ok: Boolean(compatible),
       present: true,
@@ -571,7 +561,7 @@ if (!cli.ok) {
 if (!cli.ok) {
   const rollbackFailed = installedCli && !rollbackCliInstall();
   const detail = cli.reason ?? (cli.version ? `Found ${cli.version}; supported versions are ${SUPPORTED_CLI_RANGE}.` : 'No coil executable was found.');
-  console.error(`Error: ${detail} Install ${PUBLIC_CLI_SPEC} from the public npm registry, or rerun with --cli-package <path-to-reviewed-tarball>.`);
+  console.error(`Error: ${detail} Install @usecoil/cli ${PUBLIC_CLI_SPEC} from the public npm registry, or rerun with --cli-package <path-to-reviewed-tarball>.`);
   if (rollbackFailed) console.error('Warning: automatic rollback of the newly installed Coil CLI failed; remove @usecoil/cli manually.');
   process.exit(1);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@usecoil/skill-claude",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Claude Code skill package for Coil agent workflows",
   "type": "module",
   "bin": {
@@ -28,7 +28,7 @@
   },
   "coilCompatibility": {
     "cli": "0.1.x",
-    "preferredVersion": "0.1.4"
+    "preferredVersion": "0.1.5"
   },
   "coilRuntime": {
     "name": "claude",

package/skill/SKILL.md

@@ -16,7 +16,7 @@ it can do:
 
 ```bash
 if ! command -v coil >/dev/null 2>&1; then
-  npm install --global @usecoil/cli@0.1.4
+  npm install --global @usecoil/cli@0.1.5
 fi
 coil --version
 ```
@@ -77,7 +77,7 @@ The runtime-specific installer or registry handles placement; Coil operations
 always use the same public JSON CLI:
 
 ```bash
-npm install --global @usecoil/cli@0.1.4
+npm install --global @usecoil/cli@0.1.5
 coil config set-base-url https://www.usecoil.com --profile prod
 printf '%s' "$COIL_API_KEY" | coil auth login --profile prod --key -
 coil --profile prod agent-context --json
@@ -205,23 +205,6 @@ coil --profile prod recipe-runs retry <run-id> --json
 
 Publication and ambiguous-effect reconciliation require a human organization admin. If a run has an unresolved provider effect, relay the server-provided `human_action.url` from the view/wait/watch state (or `error.details.human_action` from a machine reconcile denial) verbatim. The URL opens `/dashboard/recipe-runs/{runId}` for evidence review; it is navigation only and does not prove provider acceptance or authorize a decision. Retry/cancel behavior follows the durable run state and `next_actions`, not the presence of a URL.
 
-### Lead-list imports
-
-```bash
-coil --profile prod --json leads import ./prospects.csv --mapping '{"Work email":"email"}' --admission-key import-september-001
-coil --profile prod recipe-runs view <run-id> --json
-coil --profile prod recipe-runs import-outcomes <run-id> --outcome rejected --json
-coil --profile prod recipe-runs leads <run-id> --json
-```
-
-Imports accept at most 2,000 data rows and 2 MiB of CSV input. Use header
-mapping for ambiguous columns and a stable admission key when a retry could be
-uncertain. A `202` response means durable admission, not terminal success. Do
-not report completion until the run is terminal and its outcomes and attributed
-leads have been inspected. Rejected-row PII is not printed. Successful inputs
-are scrubbed after completion; failed or cancelled normalized replay data is
-retained for up to 30 days. The original CSV is never stored.
-
 ### Scrapes
 
 ```bash

package/skill/references/api-endpoints.md

@@ -96,20 +96,6 @@ Machine callers can create scrapes. Admin-gated destructive routes require a hum
 | PATCH | `/api/leads/bulk` | `coil leads bulk-update --ids ... --fields '{...}' --json` |
 | POST | `/api/export/csv` | `coil leads export <scrape-id> [--filter/--view/--ids] [--output]` |
 | GET | `/api/leads/emails?scrapeId={id}` | `coil leads emails <scrape-id>` |
-| POST | `/api/leads/import` | `coil --json leads import <file> [--mapping ...] [--admission-key ...]` |
-| GET | `/api/recipe-runs/{id}/import-outcomes` | `coil recipe-runs import-outcomes <run-id> --outcome rejected --json` |
-| GET | `/api/recipe-runs/{id}/leads` | `coil recipe-runs leads <run-id> --json` |
-
-Lead-list imports accept at most 2,000 data rows and 2 MiB of CSV input. The
-CLI maps supported headers before admission; use `--mapping` for ambiguous
-headers and a stable `--admission-key` when a retry may be uncertain. A `202`
-response means durable admission, not terminal success. Inspect
-`coil recipe-runs view`, `coil recipe-runs import-outcomes`, and
-`coil recipe-runs leads` and wait for a terminal run state before reporting
-completion. The API is organization-scoped, does not retain the original CSV,
-and does not print rejected-row PII. Successful inputs are scrubbed after
-completion; failed or cancelled normalized replay data is retained for up to
-30 days.
 
 ## Automations