@seliseblocks/cli-os 0.2.10 → 0.2.12

package/dist/skills/blocks-storage-configuration/SKILL.md

@@ -1,93 +0,0 @@
----
-name: blocks-storage-configuration
-description: "Configure which storage provider (Azure Blob, S3-compatible object storage, or local/SFTP storage) backs a SELISE Blocks project's file object tree: named configurations with host, port, credentials, region/endpoint or connection string, and strategy, via the blocks CLI ('storage config get/list/save/delete'). CLI-only, project-scoped admin surface. Use to create, inspect, rotate, switch, or delete provider configurations; file/directory/object operations belong to blocks-data-storage."
----
-
-# Blocks Storage — Configuration
-
-This skill manages the **storage configuration record itself** — which cloud provider (or local/SFTP storage) a named configuration points at, and the connection details needed to reach it. It does not upload, download, browse, share, version, move, or trash objects; those runtime concerns belong to blocks-data-storage.
-
-**CLI-only, no SDK path.** There is no `@seliseblocks/client` method for reading or writing a storage configuration's own fields. Runtime storage calls select an existing record by `configurationName`. If the user wants to manipulate a file/directory or its access policies, hand off to blocks-data-storage.
-
-**Prerequisite:** a project is selected (`blocks use <tenantId>`). If login/project state is unknown, run the blocks-onboarding skill first.
-
-## Command family
-
-All four commands require an **impersonated project token** — there is no account-token path for this surface, consistent with other project-scoped admin commands (`secrets *`, `data config *`, etc.).
-
-| Command | Notes |
-|---|---|
-| `blocks storage config list` | No parameters beyond the selected project. Read-only. |
-| `blocks storage config get <name>` | `<name>` (positional) or `--name` (required if no positional arg). Read-only. |
-| `blocks storage config save` | Upsert — create or update a configuration. Mutating. |
-| `blocks storage config delete <name>` | `<name>` (positional) or `--name` (required if no positional arg). Mutating. |
-
-```bash
-blocks storage config list --json
-blocks storage config get Default --json
-blocks storage config get --name Default --json
-```
-
-## `storage config save` — fields
-
-`save` builds its request body from `--body`/`--file` (a raw JSON object, spread first) merged with these convenience flags (later, so they win if both are given):
-
-| Flag | Body field |
-|---|---|
-| `--name` | `name` |
-| `--item-id` | `itemId` |
-| `--strategy` | `storageStrategy` |
-| `--host` | `host` |
-| `--port` | `port` |
-| `--region-endpoint` | `cloudStorageRegionEndPoint` |
-| `--connection-string` | `connectionString` |
-| `--access-key` | `accessKey` |
-| `--secret-key` | `secretKey` |
-| `--username` | `userName` |
-| `--password` | `password` |
-| `--remote-base-path` | `remoteBasePath` |
-| `--update` (boolean) | `updateRequest` |
-
-Unset flags are dropped (`compact`), so they never overwrite fields already present in a `--body`/`--file` payload. `save` is a create-or-update in one command, not two separate verbs — pass `--item-id` (and typically `--update`) when modifying an existing configuration, omit it to create a new one.
-
-```bash
-blocks storage config save --name Default --strategy AzureBlob \
-  --host mystorageaccount.blob.core.windows.net --region-endpoint eu-west-1 \
-  --access-key <key> --secret-key <secret> --dry-run --json
-blocks storage config save --name Default --strategy AzureBlob \
-  --host mystorageaccount.blob.core.windows.net --region-endpoint eu-west-1 \
-  --access-key <key> --secret-key <secret> --yes --json
-
-# Update an existing configuration
-blocks storage config save --item-id <id> --update --connection-string "<new connection string>" --dry-run --json
-blocks storage config save --item-id <id> --update --connection-string "<new connection string>" --yes --json
-```
-
-## `--dry-run` before `--yes` — always
-
-Both mutating commands (`save`, `delete`) follow the standard `blocks` mutation discipline: `--dry-run` prints what would be sent and returns without calling the API; `--yes` skips the interactive confirmation prompt and sends the request for real. Omitting both drops into an interactive "Type 'yes' to continue" prompt — not viable in a scripted/agent context, so always pass one or the other explicitly.
-
-```bash
-blocks storage config delete Default --dry-run --json
-blocks storage config delete Default --yes --json
-```
-
-`save`'s dry-run output redacts secret-shaped fields before printing (`accessKey`, `connectionString`, `password`, `secretKey` become `"***"`) — this redaction is **dry-run-preview only**, it does not change what's actually sent when you run with `--yes`, and it doesn't apply to `get`/`list` responses (see Gotchas).
-
-## Gotchas
-
-- **`get`/`list` are not redacted.** Only `save --dry-run`'s own preview output redacts `accessKey`/`connectionString`/`password`/`secretKey`. If a `get`/`list` response ever echoes credential fields back, treat that output as sensitive — don't paste it into logs, tickets, or chat verbatim.
-- **`save` is upsert, not separate create/update commands.** Whether a call creates or updates is determined by whether `--item-id` is present, not by a different command name.
-- **This is provider configuration, not object management.** `blocks storage config *` never touches file bytes, directory hierarchy, versions, trash, sharing, or ACLs. Those belong to **blocks-data-storage**, using a `configurationName` that a storage config already defines.
-- **No positional-or-flag ambiguity trap:** `get`/`delete` accept the configuration name as either the first positional argument or `--name`; only one is required, not both.
-- **Impersonated project token only.** Like `secrets *` and `data config *`, none of these four commands run against the account token — a project must be selected first (`blocks use <tenantId>`).
-
-## Example trigger prompts
-
-- "Set up Azure Blob storage for this project." → `storage config save --strategy AzureBlob ...`.
-- "What storage configurations exist on this project?" → `storage config list`.
-- "Show me the `Default` storage configuration." → `storage config get Default`.
-- "Rotate the access key on our storage config." → `storage config save --item-id <id> --update --access-key <new key> ...`.
-- "Switch this project to local storage." → `storage config save --strategy <local strategy value> --host ... --port ...` (confirm the exact strategy value expected by the project rather than guessing).
-- "Delete this storage configuration, we don't use it anymore." → `storage config delete <name>`.
-- "How do I actually upload a file once storage is configured?" → hand off to **blocks-data-storage**, not this skill.

package/dist/skills/lint.mjs

@@ -1,168 +0,0 @@
-#!/usr/bin/env node
-// Consistency lint for blocks-skills/. Run: node blocks-skills/lint.mjs
-//
-// A skill is consumed by an AI that has ONLY the globally-installed `blocks`
-// CLI and a project-local `@seliseblocks/client` -- never this monorepo, and
-// `blocks skill add` pulls exactly one skill directory at a time. Checks:
-// 1. Every skill directory has a SKILL.md with frontmatter: `name` matches the
-//    directory name, `name` <= 64 chars, `description` present, non-empty,
-//    on a single physical line (blocks-cli's own frontmatter parser --
-//    src/lib/skills.ts -- is a hand-rolled line-by-line parser with no YAML
-//    dependency; a description that wraps onto a second line silently breaks
-//    `blocks skill list`/`show`), and <= 1024 chars (hard fail) / <= 700 chars
-//    (warn -- this pack's house style target is ~400-600).
-// 2. Relative markdown links (in SKILL.md and any flows/*.md) resolve to a
-//    real file.
-// 3. No links leave the containing skill's own directory at all -- not into
-//    another skill's SKILL.md, not into its flows/, not to a monorepo-only
-//    file outside blocks-skills/. A skill may mention another skill BY NAME
-//    in plain text, never as a link, since the target isn't guaranteed to be
-//    present for a consumer who only pulled this one skill. Links within the
-//    same skill's own directory (SKILL.md <-> its own flows/*.md) are fine.
-// 4. No raw API endpoint paths (e.g. `/iam/v4/...`, `/os/v4/...`) -- skills
-//    describe CLI commands and SDK methods, never the wire protocol behind
-//    them; citing a path is exactly the kind of detail that could tempt a
-//    raw fetch/curl bypass every skill already forbids.
-// Exit 0 = clean, 1 = problems found (all listed, not just the first).
-import { readdirSync, readFileSync, existsSync, statSync } from "node:fs";
-import { dirname, join, relative } from "node:path";
-import { fileURLToPath } from "node:url";
-
-const skillsDir = dirname(fileURLToPath(import.meta.url));
-const errors = [];
-const warnings = [];
-
-const DESCRIPTION_HARD_LIMIT = 1024;
-const DESCRIPTION_WARN_LIMIT = 700;
-const NAME_LIMIT = 64;
-const ENDPOINT_PATTERN = /\/(iam|data|os|logic|release|localization)\/v4\/[A-Za-z0-9/{}._-]*/g;
-
-const skillDirs = readdirSync(skillsDir, { withFileTypes: true })
-  .filter((entry) => entry.isDirectory())
-  .map((entry) => entry.name)
-  .sort();
-
-for (const skillName of skillDirs) {
-  const skillPath = join(skillsDir, skillName);
-  const skillMdPath = join(skillPath, "SKILL.md");
-
-  if (!existsSync(skillMdPath)) {
-    errors.push(`${skillName}/: no SKILL.md`);
-    continue;
-  }
-
-  checkFrontmatter(skillName, skillMdPath);
-  checkLinksInFile(skillName, skillMdPath);
-  checkEndpointsInFile(skillMdPath);
-
-  const flowsDir = join(skillPath, "flows");
-  if (existsSync(flowsDir) && statSync(flowsDir).isDirectory()) {
-    for (const entry of readdirSync(flowsDir, { withFileTypes: true })) {
-      if (entry.isFile() && entry.name.endsWith(".md")) {
-        const flowPath = join(flowsDir, entry.name);
-        checkLinksInFile(skillName, flowPath);
-        checkEndpointsInFile(flowPath);
-      }
-    }
-  }
-}
-
-function checkFrontmatter(skillName, skillMdPath) {
-  const raw = readFileSync(skillMdPath, "utf8");
-  const match = raw.match(/^---\r?\n([\s\S]*?)\r?\n---\r?\n?/);
-  const rel = relative(skillsDir, skillMdPath);
-
-  if (!match) {
-    errors.push(`${rel}: missing frontmatter (expected a leading --- ... --- block)`);
-    return;
-  }
-
-  const lines = match[1].split(/\r?\n/);
-  const nameLine = lines.find((line) => line.startsWith("name:"));
-  const descLine = lines.find((line) => line.startsWith("description:"));
-
-  if (!nameLine) {
-    errors.push(`${rel}: frontmatter has no 'name' field`);
-  } else {
-    const name = nameLine.slice("name:".length).trim();
-    if (name !== skillName) {
-      errors.push(`${rel}: name '${name}' does not match directory name '${skillName}'`);
-    }
-    if (name.length > NAME_LIMIT) {
-      errors.push(`${rel}: name is ${name.length} chars, over the ${NAME_LIMIT}-char limit`);
-    }
-  }
-
-  if (!descLine) {
-    errors.push(`${rel}: frontmatter has no 'description' field`);
-    return;
-  }
-
-  const singleLineMatch = descLine.match(/^description:\s*"(.*)"\s*$/);
-  if (!singleLineMatch) {
-    errors.push(
-      `${rel}: 'description' must be a double-quoted string on a single physical line ` +
-        `(blocks-cli's frontmatter parser reads it line-by-line -- a wrapped description silently truncates)`
-    );
-    return;
-  }
-
-  const description = singleLineMatch[1];
-  if (description.length === 0) {
-    errors.push(`${rel}: 'description' is empty`);
-  } else if (description.length > DESCRIPTION_HARD_LIMIT) {
-    errors.push(`${rel}: description is ${description.length} chars, over the ${DESCRIPTION_HARD_LIMIT}-char hard limit`);
-  } else if (description.length > DESCRIPTION_WARN_LIMIT) {
-    warnings.push(`${rel}: description is ${description.length} chars, over the ${DESCRIPTION_WARN_LIMIT}-char house-style target (aim for ~400-600)`);
-  }
-}
-
-function checkLinksInFile(skillName, filePath) {
-  const raw = readFileSync(filePath, "utf8");
-  const rel = relative(skillsDir, filePath);
-  const linkPattern = /\[[^\]]*\]\(([^)]+)\)/g;
-  const fileDir = dirname(filePath);
-
-  for (const match of raw.matchAll(linkPattern)) {
-    const target = match[1].trim();
-    if (/^[a-z]+:\/\//i.test(target) || target.startsWith("#")) continue; // external URL or in-page anchor
-
-    const [pathPart] = target.split("#");
-    if (!pathPart) continue;
-
-    const resolved = join(fileDir, pathPart);
-    if (!existsSync(resolved)) {
-      errors.push(`${rel}: broken link to '${pathPart}' (resolved: ${relative(skillsDir, resolved)})`);
-      continue;
-    }
-
-    const resolvedRelToSkills = relative(skillsDir, resolved).split(/[\\/]/);
-    const targetSkill = resolvedRelToSkills[0];
-    if (targetSkill !== skillName) {
-      errors.push(
-        `${rel}: link leaves this skill's own directory ('${pathPart}') -- ` +
-          `mention other skills by name in plain text instead, never a link, since ` +
-          `'blocks skill add' only copies one skill directory at a time and the target isn't guaranteed to be present`
-      );
-    }
-  }
-}
-
-function checkEndpointsInFile(filePath) {
-  const raw = readFileSync(filePath, "utf8");
-  const rel = relative(skillsDir, filePath);
-
-  for (const match of raw.matchAll(ENDPOINT_PATTERN)) {
-    errors.push(`${rel}: raw API endpoint path '${match[0]}' -- describe the CLI command/SDK method instead, never the wire path`);
-  }
-}
-
-for (const warning of warnings) console.warn(`warning: ${warning}`);
-if (errors.length === 0) {
-  console.log(`ok: ${skillDirs.length} skills, no problems found${warnings.length ? ` (${warnings.length} warning(s) above)` : ""}`);
-  process.exit(0);
-}
-
-console.error(`${errors.length} problem(s) found:`);
-for (const error of errors) console.error(`  - ${error}`);
-process.exit(1);