Agent skill

Fieldworks Test Coverage

by sillsdev in sillsdev/FieldWorks

Check that new or changed FieldWorks code is actually exercised by tests, using test.ps1 -Coverage.

Custom licenceAuto-check passedTesting & QA

Install Fieldworks Test Coverage

skills CLI
$ npx skills add sillsdev/FieldWorks --skill fieldworks-test-coverage -a claude-code

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

GitHub CLI
$ gh skill install sillsdev/FieldWorks fieldworks-test-coverage --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/fieldworks-test-coverage .claude/skills/fieldworks-test-coverage && 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
fieldworks-test-coverage
GitHub stars
110
Token cost
~1.1k tokens
SKILL.md length
533 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
Custom licence

At a glance

Check that new or changed FieldWorks code is actually exercised by tests, using test.ps1 -Coverage.

  • Works in 4 steps: Identify the decision surface → Run coverage for the touched project(s) → Check the new lines specifically → …
  • Writing tests for a change
  • Calls choco
  • Before claiming a bug fix

What it does

Fieldworks Test Coverage is an agent skill from sillsdev/FieldWorks. Check that new or changed FieldWorks code is actually exercised by tests, using test.ps1 -Coverage. Use whenever writing tests for a change, before claiming a bug fix or feature is covered, or when reviewing whether "tests pass" also means the new logic runs under test.

Its SKILL.md is about 1.1k 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 Test coverage and Debugging. 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

  • Writing tests for a change
  • Before claiming a bug fix
  • Feature is covered
  • Reviewing whether tests pass also means the new logic runs under test

Example prompts

  • “tests pass”
  • “/fieldworks-test-coverage”

Workflow steps

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

  1. Identify the decision surface
  2. Run coverage for the touched project(s)
  3. Check the new lines specifically
  4. Close real gaps, document accepted ones

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

    Shell commands in SKILL.md call:

    • choco

    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

Fieldworks Test Coverage loads about 1.1k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 533 words of instructions outside code blocks.

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

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 533 words (~1,088 tokens).

“You confirm that new/changed behavior is exercised by tests, not merely that some test file exists nearby. "Tests pass" is not the same claim as "the new code ran during the test" — this skill closes that gap.”

— opening of SKILL.md by sillsdev, Custom licence
name
fieldworks-test-coverage
model
haiku

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/fieldworks-test-coverage of sillsdev/FieldWorks.

Open the folder on GitHubat commit 44b1d04

Compare with similar skills

Fieldworks Test Coverage 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.

Fieldworks Test Coverage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fieldworks Test Coverage this skillsillsdev/FieldWorks110—~1.1kAutomated safety check: PassCustom licence
Testingdoorkeeper-gem/doorkeeper5.5k—~1.6kAutomated safety check: PassMIT
Test Gap Auditgithub/awesome-copilot40k—~3.4kAutomated safety check: PassMIT
Test BlindspotsNeeeophytee/finding-unknowns-skills343—~676Automated safety check: PassMIT
Write Testsopenplayerjs/openplayerjs649—~1.8kAutomated safety check: PassMIT
Test Specialisttravisjneuman/.claude101—~3.7kAutomated safety check: PassMIT

Similar skills

  • Testing

    doorkeeper-gem/doorkeeper

    Write correct and complete RSpec tests for Doorkeeper. An agent skill from doorkeeper-gem/doorkeeper.

    5.5k GitHub stars~1.6k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Test Gap Audit

    github/awesome-copilot

    Official

    Run a read-only audit for missing, weak, stale, or mis-scoped test coverage.

    40k GitHub stars~3.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Test Blindspots

    Neeeophytee/finding-unknowns-skills

    Find consequential behavior that a passing test suite does not establish, using focused exploratory checks.

    343 GitHub stars~676 tokensUpdated 9 days ago
    Testing & QAAuto-check passed
  • Write Tests

    openplayerjs/openplayerjs

    Write or extend Jest tests for OpenPlayerJS to this repo's exact conventions — makeCore factories, typed internals handles instead of as any, media property mocking, fake timers, ads/vast mocks, and…

    649 GitHub stars~1.8k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Test Specialist

    travisjneuman/.claude

    Test-writing patterns for JS/TS, Python, Go, and Rust (unit, integration, E2E, visual regression).

    101 GitHub stars~3.7k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Test Debugging

    ruby-git/ruby-git

    Debugs failing or flaky tests and improves test coverage. An agent skill from ruby-git/ruby-git.

    1.8k GitHub stars~1.5k tokensUpdated 5 days ago
    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 today
    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 today
    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 today
    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 today
    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 today
    Auto-check passed
  • 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 today
    Auto-check passed

Questions about Fieldworks Test Coverage

What does Fieldworks Test Coverage do?

Check that new or changed FieldWorks code is actually exercised by tests, using test.ps1 -Coverage. Fieldworks Test Coverage is an agent skill from sillsdev/FieldWorks.ps1 -Coverage.

When should I use Fieldworks Test Coverage?

Fieldworks Test Coverage fits situations like: writing tests for a change; before claiming a bug fix; feature is covered; reviewing whether tests pass also means the new logic runs under test.

How do I install Fieldworks Test Coverage in Claude Code?

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

How do I install Fieldworks Test Coverage in Codex?

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

Can I use Fieldworks Test Coverage 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 fieldworks-test-coverage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fieldworks-test-coverage, .gemini/skills/fieldworks-test-coverage, .github/skills/fieldworks-test-coverage and .opencode/skills/fieldworks-test-coverage in your project.

What does Fieldworks Test Coverage need to run?

Going by SKILL.md and its folder, Fieldworks Test Coverage needs the command-line tools its instructions call (choco).

Does Fieldworks Test Coverage 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 Fieldworks Test Coverage 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 Fieldworks Test Coverage use?

Fieldworks Test Coverage 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 Fieldworks Test Coverage use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Fieldworks Test Coverage?

Skills that share tags, products or a category with Fieldworks Test Coverage: Testing (doorkeeper-gem/doorkeeper, 5.5k stars), Test Gap Audit (github/awesome-copilot, 40k stars), Test Blindspots (Neeeophytee/finding-unknowns-skills, 343 stars) and Write Tests (openplayerjs/openplayerjs, 649 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fieldworks Test Coverage?

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.