Agent skill

CLI E2E Test Authoring

Guide for adding new end-to-end tests for the Packmind CLI. An agent skill from PackmindHub/packmind.

Apache-2.0Auto-check passedTesting & QA

Install CLI E2E Test Authoring

skills CLI

$ npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind cli-e2e-test-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cli-e2e-test-authoring .claude/skills/cli-e2e-test-authoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cli-e2e-test-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/cli-e2e-test-authoring into .claude/skills/cli-e2e-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-e2e-test-authoring", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/PackmindHub/packmind/tree/main/.agents/skills/cli-e2e-test-authoring

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind cli-e2e-test-authoring --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/cli-e2e-test-authoring .agents/skills/cli-e2e-test-authoring && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cli-e2e-test-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/cli-e2e-test-authoring into .agents/skills/cli-e2e-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-e2e-test-authoring", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind cli-e2e-test-authoring --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/cli-e2e-test-authoring .cursor/skills/cli-e2e-test-authoring && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cli-e2e-test-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/cli-e2e-test-authoring into .cursor/skills/cli-e2e-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-e2e-test-authoring", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/PackmindHub/packmind.git --path .agents/skills/cli-e2e-test-authoring

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind cli-e2e-test-authoring --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/cli-e2e-test-authoring .gemini/skills/cli-e2e-test-authoring && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cli-e2e-test-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/cli-e2e-test-authoring into .gemini/skills/cli-e2e-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-e2e-test-authoring", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install PackmindHub/packmind cli-e2e-test-authoring

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/cli-e2e-test-authoring .github/skills/cli-e2e-test-authoring && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cli-e2e-test-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/cli-e2e-test-authoring into .github/skills/cli-e2e-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-e2e-test-authoring", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install PackmindHub/packmind cli-e2e-test-authoring --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/cli-e2e-test-authoring .opencode/skills/cli-e2e-test-authoring && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cli-e2e-test-authoring" agent skill from https://github.com/PackmindHub/packmind/tree/main/.agents/skills/cli-e2e-test-authoring into .opencode/skills/cli-e2e-test-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-e2e-test-authoring", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cli-e2e-test-authoring
GitHub stars: 317
Token cost: ~1.6k tokens
SKILL.md length: 399 words
Files: 1
Skills in repo: 35
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Guide for adding new end-to-end tests for the Packmind CLI. An agent skill from PackmindHub/packmind.

Works in 4 steps: Add the interface method to… → Create… → Add a lazy getter to… → …
Tasks that involve End-to-end testing
SKILL.md covers Overview, Test File Location, Choosing a Test Wrapper and Setting Up Test Preconditions, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

CLI E2E Test Authoring is an agent skill from PackmindHub/packmind. Guide for adding new end-to-end tests for the Packmind CLI. This skill should be used when creating new test specs in the apps/cli-e2e-tests/ directory that exercise CLI commands against a real binary and API.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing. It works with Git. The repository describes itself as: Packmind seamlessly captures your engineering playbook and turns it into AI context, guardrails, and governance. The licence is Apache-2.0.

When your agent uses it

Tasks that involve End-to-end testing

Example prompts

“/cli-e2e-test-authoring”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Add the interface method to helpers/IPackmindGateway.ts. All exposed methods must be typed with Gateway or PublicGateway (imported from…
Create helpers/gateways/NewResourceGateway.ts implementing the interface
Add a lazy getter to helpers/gateways/PackmindGateway.ts (reset on initializeWithApiKey)
Re-export from helpers/index.ts

What it can do on your machine

Read from SKILL.md and the folder at commit 858ed50. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CLI E2E Test Authoring loads about 1.6k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 399 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from PackmindHub/packmind at commit 858ed50, republished under its Apache-2.0 licence (© PackmindHub). 399 words, ~1,575 tokens.

Download SKILL.mdSave it as .claude/skills/cli-e2e-test-authoring/SKILL.md (or your agent's skills folder).

name: cli-e2e-test-authoring
description: Guide for adding new end-to-end tests for the Packmind CLI. This skill should be used when creating new test specs in the `apps/cli-e2e-tests/` directory that exercise CLI commands against a real binary and API.

CLI E2E Test Authoring

Overview

Add end-to-end tests that exercise the Packmind CLI binary (dist/apps/cli/main.cjs) in realistic conditions. Tests run the actual CLI as a child process and, when authentication is needed, interact with a running API via HTTP gateways.

Test File Location

All spec files live in apps/cli-e2e-tests/src/ and follow the naming convention <command>.spec.ts.

Choosing a Test Wrapper

Two wrappers are available depending on whether the command requires authentication.

Unauthenticated commands — `describeWithTempSpace`

Provides an isolated temporary directory. No API required.

typescript

import { describeWithTempSpace, runCli } from './helpers';

describeWithTempSpace('my-command without auth', (getContext) => {
  let result: Awaited<ReturnType<typeof runCli>>;

  beforeEach(async () => {
    const { testDir } = await getContext();
    result = await runCli('my-command', { cwd: testDir });
  });

  it('exits with code 1', () => {
    expect(result.returnCode).toBe(1);
  });

  it('shows an error message', () => {
    expect(result.stdout).toContain('No credentials found');
  });
});

Authenticated commands — `describeWithUserSignedUp`

Extends describeWithTempSpace by creating a real user account, signing in, and generating an API key. Requires a running API at http://localhost:4200.

typescript

import { describeWithUserSignedUp, runCli } from './helpers';

describeWithUserSignedUp('my-command with auth', (getContext) => {
  let result: Awaited<ReturnType<typeof runCli>>;

  beforeEach(async () => {
    const { apiKey, testDir } = await getContext();
    result = await runCli('my-command', { apiKey, cwd: testDir });
  });

  it('succeeds', () => {
    expect(result.returnCode).toBe(0);
  });

  it('displays expected output', () => {
    expect(result.stdout).toContain('Expected text');
  });
});

The context object from describeWithUserSignedUp provides:

Field	Description
`testDir`	Isolated temporary directory
`apiKey`	Valid API key for the created user
`user`	User object (email, etc.)
`organization`	Organization the user belongs to
`spaceId`	Global space ID for the organization
`gateway`	Authenticated gateway to call the API directly

Setting Up Test Preconditions

Git repository

Commands that interact with git (e.g. diff, install) require a git repo. Call setupGitRepo in beforeEach:

typescript

import { setupGitRepo } from './helpers';

beforeEach(async () => {
  const { testDir } = await getContext();
  await setupGitRepo(testDir);
});

Creating API resources

Use gateway from the context to seed data before running the CLI:

typescript

beforeEach(async () => {
  const { gateway, spaceId, testDir } = await getContext();
  await setupGitRepo(testDir);
  await gateway.commands.create({ spaceId, /* ... */ });
  await gateway.packages.create({ spaceId, /* ... */ });
});

File manipulation

Use file helpers to create or modify files in the test directory:

typescript

import { readFile, updateFile, fileExists } from './helpers';

const content = readFile('path/to/file.md', testDir);
updateFile('path/to/file.md', 'new content', testDir);
const exists = fileExists('path/to/file.md', testDir);

Assertion Patterns

Split assertions into individual it blocks. Store the CLI result in a block-scoped let variable populated by beforeEach:

typescript

let result: Awaited<ReturnType<typeof runCli>>;

beforeEach(async () => {
  result = await runCli('some-command', { apiKey, cwd: testDir });
});

it('succeeds', () => {
  expect(result.returnCode).toBe(0);
});

it('displays the summary', () => {
  expect(result.stdout).toContain('1 change submitted');
});

Nesting Describes for Multi-Step Scenarios

For commands that require chained operations (e.g. install then modify then diff), nest describe blocks. Each level adds its own beforeEach that builds on the parent context:

typescript

describeWithUserSignedUp('diff command', (getContext) => {
  beforeEach(async () => {
    // setup: git repo + seed data + install
  });

  describe('when a change is submitted', () => {
    beforeEach(async () => {
      // modify file + run diff --submit
    });

    it('succeeds', () => { /* ... */ });

    describe('when running diff again', () => {
      beforeEach(async () => {
        // run diff without --submit
      });

      it('excludes the already-submitted change', () => { /* ... */ });
    });
  });
});

Show full SKILL.md (145 more words)Show less

Feature Flags

Before writing the test, ask the user: "Is the feature under test gated by a feature flag?"

If yes, the test must create a user whose email is at @packmind.com so the flag is enabled. This is controlled by the underFeatureFlag fixture option. Add .use({ underFeatureFlag: true }) immediately after the test wrapper import, before any describe or it blocks:

typescript

// When using testWithApi:
testWithApi.use({ underFeatureFlag: true });

// When using testWithUserSignedUp:
testWithUserSignedUp.use({ underFeatureFlag: true });

Without this option, the fixture creates a user at @example.com, which does not have feature flags enabled, and the feature under test would not be accessible.

Adding a New Gateway

When the CLI command under test requires seeding a new type of API resource:

Add the interface method to helpers/IPackmindGateway.ts. All exposed methods must be typed with Gateway<IXxxUseCase> or PublicGateway<IXxxUseCase> (imported from @packmind/types)
Create helpers/gateways/NewResourceGateway.ts implementing the interface
Add a lazy getter to helpers/gateways/PackmindGateway.ts (reset on initializeWithApiKey)
Re-export from helpers/index.ts

Files

Just SKILL.md in .agents/skills/cli-e2e-test-authoring of PackmindHub/packmind.

Open the folder on GitHubat commit 858ed50

Compare with similar skills

CLI E2E Test Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CLI E2E Test Authoring compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
CLI E2E Test Authoring this skillPackmindHub/packmind	317	—	~1.6k	Automated safety check: Pass	Apache-2.0	yesterday
OpenHarness End-to-End EvalsHKUDS/OpenHarness	16k	1 repos	~2.1k	Automated safety check: Notes	MIT	4 mo ago
Nemoclaw Maintainer Fix E2E FailuresNVIDIA/NemoClaw	23k	—	~2.6k	Automated safety check: Pass	Apache-2.0	today
Releaselycorp-jp/sim-use	1.4k	—	~1.7k	Automated safety check: Pass	Apache-2.0	yesterday
Diff-Driven Smoke TestsSkyvern-AI/skyvern	23k	—	~5.2k	Automated safety check: Pass	AGPL-3.0	today
Test Pyramidkubernetes-sigs/agent-sandbox	4.2k	—	~1.6k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
16k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check: notes
Nemoclaw Maintainer Fix E2E Failures
NVIDIA/NemoClaw
Official
Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.
23k GitHub stars~2.6k tokensUpdated today
Testing & QAAuto-check passed
Release
lycorp-jp/sim-use
Cut a sim-use release end-to-end. An agent skill from lycorp-jp/sim-use.
1.4k GitHub stars~1.7k tokensUpdated yesterday
Testing & QAAuto-check passed
Diff-Driven Smoke Tests
Skyvern-AI/skyvern
Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.
23k GitHub stars~5.2k tokensUpdated today
Testing & QAAuto-check passed
Test Pyramid
kubernetes-sigs/agent-sandbox
Official
Analyze the repo's unit and E2E tests and propose rebalancing toward a test pyramid — which E2E tests (or assertions inside them) can be covered by unit tests, which unit-level gaps genuinely need…
4.2k GitHub stars~1.6k tokensUpdated yesterday
Testing & QAAuto-check passed
E2E Test
crowdin/crowdin-api-client-js
Run end-to-end tests against the real Crowdin or Crowdin Enterprise API using credentials from .env.
139 GitHub stars~893 tokensUpdated 5 days ago
Testing & QAAuto-check: notes

More from PackmindHub/packmind

All 35 skills in this repo

Michel CLI Demo Recorder
PackmindHub/packmind
Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR.
317 GitHub stars~3.4k tokensUpdated yesterday
Auto-check passed
Michel UI Demo Recorder
PackmindHub/packmind
Record polished UI demo videos and screenshots of a running web app using Playwright MCP — for client deliverables, release notes, feature walkthroughs, or bug repros.
317 GitHub stars~6.4k tokensUpdated yesterday
Auto-check passed
Packmind Create Skill
PackmindHub/packmind
Guide for creating effective skills. An agent skill from PackmindHub/packmind.
317 GitHub stars~3.5k tokensUpdated yesterday
Auto-check: notes
Doc Audit
PackmindHub/packmind
Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage.
317 GitHub stars~2.4k tokensUpdated yesterday
Auto-check passed
Feature Sprint
PackmindHub/packmind
Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.
317 GitHub stars~1.9k tokensUpdated yesterday
Auto-check passed
Michel Packmind Engineer Review
PackmindHub/packmind
Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping…
317 GitHub stars~2.7k tokensUpdated yesterday
Auto-check passed

Works with

Questions about CLI E2E Test Authoring

What does CLI E2E Test Authoring do?

Guide for adding new end-to-end tests for the Packmind CLI. An agent skill from PackmindHub/packmind. CLI E2E Test Authoring is an agent skill from PackmindHub/packmind. Guide for adding new end-to-end tests for the Packmind CLI.

When should I use CLI E2E Test Authoring?

CLI E2E Test Authoring fits situations like: tasks that involve End-to-end testing.

How do I install CLI E2E Test Authoring in Claude Code?

Run `npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a claude-code`. Or copy the skill folder (.agents/skills/cli-e2e-test-authoring in PackmindHub/packmind) into .claude/skills/cli-e2e-test-authoring in your project. Claude Code loads it when a task matches its description.

How do I install CLI E2E Test Authoring in Codex?

Run `npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a codex`. Or copy the skill folder (.agents/skills/cli-e2e-test-authoring in PackmindHub/packmind) into .agents/skills/cli-e2e-test-authoring in your project. Codex loads it when a task matches its description.

Can I use CLI E2E Test Authoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PackmindHub/packmind --skill cli-e2e-test-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cli-e2e-test-authoring, .gemini/skills/cli-e2e-test-authoring, .github/skills/cli-e2e-test-authoring and .opencode/skills/cli-e2e-test-authoring in your project.

What does CLI E2E Test Authoring need to run?

SKILL.md names no scripts, command-line tools or credentials: CLI E2E Test Authoring is instructions for the agent only.

Does CLI E2E Test Authoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is CLI E2E Test Authoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does CLI E2E Test Authoring use?

CLI E2E Test Authoring is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CLI E2E Test Authoring use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to CLI E2E Test Authoring?

Skills that share tags, products or a category with CLI E2E Test Authoring: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Nemoclaw Maintainer Fix E2E Failures (NVIDIA/NemoClaw, 23k stars), Release (lycorp-jp/sim-use, 1.4k stars) and Diff-Driven Smoke Tests (Skyvern-AI/skyvern, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CLI E2E Test Authoring?

PackmindHub (a GitHub organization) maintains it in PackmindHub/packmind, which has 317 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 6, 2026.

Source: PackmindHub/packmind on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install CLI E2E Test Authoring

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CLI E2E Test Authoring

Overview

Test File Location

Choosing a Test Wrapper

Unauthenticated commands — describeWithTempSpace

Authenticated commands — describeWithUserSignedUp

Setting Up Test Preconditions

Git repository

Creating API resources

File manipulation

Assertion Patterns

Nesting Describes for Multi-Step Scenarios

Feature Flags

Adding a New Gateway

Files

Compare with similar skills

Similar skills

More from PackmindHub/packmind

Related

Questions about CLI E2E Test Authoring

Unauthenticated commands — `describeWithTempSpace`

Authenticated commands — `describeWithUserSignedUp`