Skip to content

nanocoai/nanoclaw / .claude/skills/add-vercel

add-vercel

Verified

Add Vercel deployment capability to NanoClaw agents. Installs the Vercel CLI in agent containers and sets up OneCLI credential injection for api.vercel.com. Use when the user wants agents to deploy web applications to Vercel.

FileKindSize
REMOVE.mdmarkdown2.4 KB
SKILL.mdskill md10.4 KB
vercel-manifest.test.tsscript2.3 KB

vercel-manifest.test.ts

View on GitHub
/**
 * Dependency guard for the Vercel CLI integration point (host tree, vitest).
 *
 * add-vercel installs the `vercel` CLI into the agent image by appending to
 * `container/cli-tools.json`, and drops its container skill into
 * `container/skills/vercel-cli/`. A globally-installed CLI binary is not
 * importable or typed, so neither `tsc` nor a runtime import can catch its
 * removal — only an image build would, and the skill's validate step does not
 * rebuild the image in CI. This structural test stands in for that leg.
 *
 * It checks both halves, because either alone is a broken install: a manifest
 * entry with no skill leaves the agent a binary it was never told about, and a
 * skill with no manifest entry tells the agent to run a command that is not
 * there.
 *
 * Supersedes `vercel-dockerfile.test.ts`, which asserted an `ARG VERCEL_VERSION`
 * / `pnpm install -g vercel@…` pair in the Dockerfile. That shape stopped
 * existing when cli-tools.json took over the global CLIs, so the old guard was
 * asserting against a file that no longer decides anything.
 */
import fs from 'fs';
import path from 'path';

import { describe, it, expect } from 'vitest';

/** Repo root — the dir holding container/, wherever this file is copied to. */
function repoRoot(): string {
  let dir = __dirname;
  for (let i = 0; i < 8; i++) {
    if (fs.existsSync(path.join(dir, 'container', 'cli-tools.json'))) return dir;
    dir = path.dirname(dir);
  }
  throw new Error('container/cli-tools.json not found walking up from ' + __dirname);
}

describe('the Vercel CLI is installed in the agent image', () => {
  const root = repoRoot();
  const manifest = JSON.parse(
    fs.readFileSync(path.join(root, 'container', 'cli-tools.json'), 'utf8'),
  ) as Array<{ name: string; version: string }>;

  it('appears in the CLI manifest', () => {
    expect(manifest.map((t) => t.name)).toContain('vercel');
  });

  it('is pinned to an exact version, so the supply-chain policy still applies', () => {
    const vercel = manifest.find((t) => t.name === 'vercel');
    expect(vercel?.version).toMatch(/^\d+\.\d+\.\d+(?:[-+][0-9A-Za-z.-]+)?$/);
  });

  it('ships its container skill, so the agent knows the CLI is there', () => {
    expect(fs.existsSync(path.join(root, 'container', 'skills', 'vercel-cli', 'SKILL.md'))).toBe(
      true,
    );
  });
});
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall