New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Create Integration Test

by sillsdev in sillsdev/FieldWorks

Turn a [class]-integration-test-plan.md into headless integration tests, one per plan item, each driving the scenario, asserting the outcome, and capturing a labeled snapshot.

Custom licenceAuto-check passedTesting & QA

Install Create Integration Test

skills CLI
$ npx skills add sillsdev/FieldWorks --skill create-integration-test -a claude-code

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

GitHub CLI
$ gh skill install sillsdev/FieldWorks create-integration-test --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/sillsdev/FieldWorks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-integration-test .claude/skills/create-integration-test && 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/

Facts

Skill name
create-integration-test
GitHub stars
110
Token cost
~761 tokens
SKILL.md length
340 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
Custom licence

At a glance

Turn a [class]-integration-test-plan.md into headless integration tests, one per plan item, each driving the scenario, asserting the outcome, and capturing a labeled snapshot.

  • Works in 3 steps: Drives the scenario with the headless… → Asserts the behavioral outcome in code… → Captures a labeled snapshot as…
  • TDD before implementation
  • SKILL.md covers What each plan item becomes, Where tests land and Process
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create Integration Test is an agent skill from sillsdev/FieldWorks. Turn a [class]-integration-test-plan.md into headless integration tests, one per plan item, each driving the scenario, asserting the outcome, and capturing a labeled snapshot. Use for TDD before implementation or as verification after it, whenever a test plan exists under Docs/migration/working/.

Its SKILL.md is about 760 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 Integration testing. The repository describes itself as: FieldWorks is a suite of software tools for language and cultural data, with support for complex scripts.

When your agent uses it

  • TDD before implementation
  • As verification after it
  • Whenever a test plan exists under Docs/migration/working/

Example prompts

  • “/create-integration-test”

Workflow steps

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

  1. Drives the scenario with the headless input pipeline (typing, focus,
  2. Asserts the behavioral outcome in code -- this is the pass/fail gate
  3. Captures a labeled snapshot as reviewable evidence

What it can do on your machine

Read from SKILL.md and the folder at commit 44b1d04. 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.

    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

Create Integration Test loads about 761 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 340 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 340 words (~761 tokens).

“Consumes the test plan a convert-* skill produced with the developer and turns it into real tests, one plan item at a time. Plans exist for dialogs, slices, AND owned controls (a control converted through the custom-control sub-cycle gets its…”

— opening of SKILL.md by sillsdev, Custom licence
name
create-integration-test

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/create-integration-test of sillsdev/FieldWorks.

Open the folder on GitHubat commit 44b1d04

Compare with similar skills

Create Integration Test 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.

Create Integration Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Integration Test this skillsillsdev/FieldWorks110—~761Automated safety check: PassCustom licence
Plugin Testingpolyipseity/obsidian-terminal948—~828Automated safety check: PassAGPL-3.0
Create Modulecartography-cncf/cartography4.1k—~2.5kAutomated safety check: PassApache-2.0
Td Integration Testmarcus/td250—~1.2kAutomated safety check: PassMIT
Integration E2E Testingshinpr/claude-code-workflows690—~3.5kAutomated safety check: PassMIT
JS-in-HTML Testingliaohch3/claude-tap3.3k—~924Automated safety check: PassMIT

Similar skills

  • Plugin Testing

    polyipseity/obsidian-terminal

    Skill for testing Obsidian plugin features in this repository.

    948 GitHub stars~828 tokensUpdated 4 days ago
    Testing & QAAuto-check passed

  • Create Module

    cartography-cncf/cartography

    Author a new Cartography intel module end-to-end (entry point, sync GET/TRANSFORM/LOAD/CLEANUP, declarative data model, integration test, schema docs).

    4.1k GitHub stars~2.5k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Td Integration Test

    marcus/td

    Write integration tests for the td-sync admin API using the TestHarness in internal/api/testharnesstest.go.

    250 GitHub stars~1.2k tokensUpdated 7 days ago
    Testing & QAAuto-check passed

  • Integration E2E Testing

    shinpr/claude-code-workflows

    Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.

    690 GitHub stars~3.5k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • JS-in-HTML Testing

    liaohch3/claude-tap

    Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.

    3.3k GitHub stars~924 tokensUpdated 15 days ago
    Testing & QAAuto-check passed

  • Crosvm Testing

    google/crosvm

    Official

    Skill to assist with running tests and managing test VMs in the crosvm repository.

    1.3k GitHub stars~847 tokensUpdated today
    Testing & QAAuto-check passed

More from sillsdev/FieldWorks

All 29 skills in this repo

  • Atlassian Readonly Skills

    sillsdev/FieldWorks

    Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.

    110 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Atlassian Skills

    sillsdev/FieldWorks

    Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.

    110 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Fieldworks Winapp

    sillsdev/FieldWorks

    Control and document the FieldWorks desktop application with WinForms MCP or WinApp MCP.

    110 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Convert Slice

    sillsdev/FieldWorks

    Drive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement.

    110 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

  • Dependabot Consolidation

    sillsdev/FieldWorks

    Combine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy…

    110 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed

  • Fieldworks Semantic Render Parity

    sillsdev/FieldWorks

    Capture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR.

    110 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Create Integration Test

What does Create Integration Test do?

Turn a [class]-integration-test-plan.md into headless integration tests, one per plan item, each driving the scenario, asserting the outcome, and capturing a labeled snapshot. Create Integration Test is an agent skill from sillsdev/FieldWorks.md into headless integration tests, one per plan item, each driving the scenario, asserting the outcome, and capturing a labeled snapshot.

When should I use Create Integration Test?

Create Integration Test fits situations like: TDD before implementation; as verification after it; whenever a test plan exists under Docs/migration/working/.

How do I install Create Integration Test in Claude Code?

Run `npx skills add sillsdev/FieldWorks --skill create-integration-test -a claude-code`. Or copy the skill folder (.claude/skills/create-integration-test in sillsdev/FieldWorks) into .claude/skills/create-integration-test in your project. Claude Code loads it when a task matches its description.

How do I install Create Integration Test in Codex?

Run `npx skills add sillsdev/FieldWorks --skill create-integration-test -a codex`. Or copy the skill folder (.claude/skills/create-integration-test in sillsdev/FieldWorks) into .agents/skills/create-integration-test in your project. Codex loads it when a task matches its description.

Can I use Create Integration Test 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 sillsdev/FieldWorks --skill create-integration-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-integration-test, .gemini/skills/create-integration-test, .github/skills/create-integration-test and .opencode/skills/create-integration-test in your project.

What does Create Integration Test need to run?

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

Does Create Integration Test 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 Create Integration Test 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 Create Integration Test use?

Create Integration Test has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Create Integration Test use?

About 761 tokens (SKILL.md is roughly 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 Create Integration Test?

Skills that share tags, products or a category with Create Integration Test: Plugin Testing (polyipseity/obsidian-terminal, 948 stars), Create Module (cartography-cncf/cartography, 4.1k stars), Td Integration Test (marcus/td, 250 stars) and Integration E2E Testing (shinpr/claude-code-workflows, 690 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Integration Test?

sillsdev (a GitHub organization) maintains it in sillsdev/FieldWorks, which has 110 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

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