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

Start Work

by druxt in druxt/druxt.js

Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test.

MITAuto-check passedTesting & QA

Install Start Work

skills CLI
$ npx skills add druxt/druxt.js --skill start-work -a claude-code

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

GitHub CLI
$ gh skill install druxt/druxt.js start-work --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/druxt/druxt.js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/start-work .claude/skills/start-work && 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
start-work
GitHub stars
114
Token cost
~887 tokens
SKILL.md length
451 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test.

  • Works in 4 steps: Find or open the issue → Branch from develop → Write the spec → …
  • Starting work on an issue
  • SKILL.md covers 1. Find or open the issue, 2. Branch from develop, 3. Write the spec and 4. Write the failing test first, plus 1 more section
  • Calls git and yarn

What it does

Start Work is an agent skill from druxt/druxt.js. Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test. Use when starting work on an issue, bug or feature in druxt.js, or when asked to change package code and no branch or issue exists yet.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/tests.yaml`).

It sits in Testing & QA, covering Failing and flaky tests. It works with Vue.js and Nuxt. The repository describes itself as: The Fully Decoupled Drupal Framework. The licence is MIT.

When your agent uses it

  • Starting work on an issue
  • Feature in druxt.js
  • Asked to change package code and no branch
  • Issue exists yet

Example prompts

  • “/start-work”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Find or open the issue
  2. Branch from develop
  3. Write the spec
  4. Write the failing test first

What it can do on your machine

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

    • git
    • yarn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and yarn, which can reach the network depending on how they are called.

    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

Start Work loads about 887 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 451 words of instructions outside code blocks.

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

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 druxt/druxt.js at commit b07a3e3, republished under its MIT licence (© druxt). 451 words, ~887 tokens.

Download SKILL.mdSave it as .claude/skills/start-work/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
start-work
description
Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test. Use when starting work on an issue, bug or feature in druxt.js, or when asked to change package code and no branch or issue exists yet.

Start work

Every change to druxt.js goes through the same steps, whoever writes it. Do them in order and stop at a step that needs the person you work for.

1. Find or open the issue

Search the open and closed issues on druxt/druxt.js for the problem first. If one exists, work from it. If none does, draft one from the matching template in .github/ISSUE_TEMPLATE/ and ask the person you work for to open it, or open it yourself when they have asked you to.

2. Branch from develop

develop is the integration branch. main takes release merges only.

bash
git remote -v          # upstream = druxt/druxt.js, origin = your fork
git remote add upstream https://github.com/druxt/druxt.js.git   # if upstream is missing
git fetch upstream develop
git checkout -b feature/<issue>-<short-description> upstream/develop

Fill in the issue number and a short description, and say the full branch name, such as feature/412-empty-menu, before you create it. On a clone of druxt/druxt.js itself there is no fork, so use origin in place of upstream. The branch prefix is feature/ for fixes and features alike, never feat/.

Your work goes on this branch, even when your environment names another branch to push to, such as a hosted session's default branch. Keep commits off develop and off any shared base branch.

Check that git config user.name and git config user.email are those of the person you work for. Commits are made under their identity, never an agent's, and the hooks refuse an agent's.

3. Write the spec

Skip this for a one-line fix. For anything larger, write a spec in the issue or the pull request description and get it signed off before writing code:

markdown
## Goal

One sentence: what this changes for a Druxt user.

## Acceptance criteria

- Specific and testable.

## In scope

## Out of scope

## Open questions

Out of scope lists what you will leave alone. Keep to it, and raise anything new as a question or a follow-up issue.

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

4. Write the failing test first

Unit tests sit in each package's test/ directory, beside the source they cover (such as packages/router/test/router.test.js). Write the test, then run it and watch it fail for the reason you expect. The tests load built packages (druxt-test-utils imports druxt from its dist/ output), so build once first:

bash
yarn build
yarn test:unit packages/router

A test that passes before the fix does not test the fix.

Ground rules

  • The toolchain is pinned to Node 16, Yarn 3, Vue 2.7, Nuxt 2, jest 29 and eslint 7. Leave it alone unless the issue is the upgrade itself.
  • Druxt components use the Vue 2 Options API. Advice written for Vue 3 or Nuxt 3/4 (<script setup>, composables, Nitro) does not apply here.
  • Commits follow Conventional Commits. The scope is the issue number when there is one (fix(#412): …, feat(#412): …), and otherwise the package name (fix(router): …).
  • Every @param in JSDoc needs a {type} and a - description. The JSDoc is the published API reference.

Next, write the change, then use the add-changeset skill if a published package changed, and the verify-change skill before opening a pull request.

© druxt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/start-work of druxt/druxt.js.

  • SKILL.md
  • evals/tests.yaml

Open the folder on GitHubat commit b07a3e3

Compare with similar skills

Start Work 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.

Start Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Start Work this skilldruxt/druxt.js114—~887Automated safety check: PassMIT
Site Bug Huntdebs-obrien/debbie.codes142—~1.2kAutomated safety check: PassNone
Verify Debbie Codesdebs-obrien/debbie.codes142—~1.9kAutomated safety check: PassNone
Vue Nuxtericrisco/rsc-harness156—~4.2kAutomated safety check: PassMIT
Domscribepatchorbit/domscribe193—~3.3kAutomated safety check: NotesMIT
Review DocsTotomInc/vue3-select-component119—~3.8kAutomated safety check: PassMIT

Similar skills

  • Site Bug Hunt

    debs-obrien/debbie.codes

    Exploratory QA for debbie.codes. An agent skill from debs-obrien/debbie.codes.

    142 GitHub stars~1.2k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • Verify Debbie Codes

    debs-obrien/debbie.codes

    Drive the live debbie.codes Nuxt site (web UI) the way a user does via Playwright — launch the dev server, doctor health, exercise mapped features, capture screenshots/ARIA evidence, and clean up.

    142 GitHub stars~1.9k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • Vue Nuxt

    ericrisco/rsc-harness

    A skill your agent uses when building or reviewing a Vue 3 + Nuxt 4 app — <script setup reactivity, SSR/SSG/hybrid routeRules, the app/+server/ layout, SSR-safe fetching (useFetch/useAsyncData) and…

    156 GitHub stars~4.2k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Domscribe

    patchorbit/domscribe

    Work with Domscribe — the pixel-to-code bridge. An agent skill from patchorbit/domscribe.

    193 GitHub stars~3.3k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check: notes

  • Review Docs

    TotomInc/vue3-select-component

    Review documentation for quality, clarity, SEO, and technical correctness.

    119 GitHub stars~3.8k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

  • PDF Vue3

    hymhub/pdf-vue3

    Use the pdf-vue3 Vue 3 component to render PDFs (URL, base64, or Uint8Array) with built-in virtual scrolling, crisp zoom, print, download, and page navigation.

    123 GitHub stars~1k tokensUpdated 4 mo ago
    Documents & OfficeAuto-check passed

More from druxt/druxt.js

  • Add Changeset

    druxt/druxt.js

    Writes the changeset that versions a druxt.js package change and becomes its changelog entry.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed

  • Address Review

    druxt/druxt.js

    Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply.

    114 GitHub stars~600 tokensUpdated today
    Auto-check passed

  • Open PR

    druxt/druxt.js

    Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in.

    114 GitHub stars~771 tokensUpdated today
    Auto-check passed

  • Triage Issue

    druxt/druxt.js

    Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed

  • Verify Change

    druxt/druxt.js

    Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results.

    114 GitHub stars~916 tokensUpdated today
    Auto-check passed

  • Write Skill

    druxt/druxt.js

    Creates or changes a druxt.js contributor skill in .agents/skills, with its evals and the tests that gate it.

    114 GitHub stars~926 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Start Work

What does Start Work do?

Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test. js.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test.

When should I use Start Work?

Start Work fits situations like: starting work on an issue; feature in druxt.js; asked to change package code and no branch; issue exists yet.

How do I install Start Work in Claude Code?

Run `npx skills add druxt/druxt.js --skill start-work -a claude-code`. Or copy the skill folder (.agents/skills/start-work in druxt/druxt.js) into .claude/skills/start-work in your project. Claude Code loads it when a task matches its description.

How do I install Start Work in Codex?

Run `npx skills add druxt/druxt.js --skill start-work -a codex`. Or copy the skill folder (.agents/skills/start-work in druxt/druxt.js) into .agents/skills/start-work in your project. Codex loads it when a task matches its description.

Can I use Start Work 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 druxt/druxt.js --skill start-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/start-work, .gemini/skills/start-work, .github/skills/start-work and .opencode/skills/start-work in your project.

What does Start Work need to run?

Going by SKILL.md and its folder, Start Work needs the command-line tools its instructions call (git and yarn).

Does Start Work access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Start Work 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 Start Work use?

Start Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Start Work use?

About 887 tokens (SKILL.md is roughly 3.5k 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 Start Work?

Skills that share tags, products or a category with Start Work: Site Bug Hunt (debs-obrien/debbie.codes, 142 stars), Verify Debbie Codes (debs-obrien/debbie.codes, 142 stars), Vue Nuxt (ericrisco/rsc-harness, 156 stars) and Domscribe (patchorbit/domscribe, 193 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Start Work?

druxt (a GitHub organization) maintains it in druxt/druxt.js, which has 114 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

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