Ha Frontend Testing
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests.
Install Typescript Testing
$ npx skills add ComposioHQ/composio --skill typescript-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ComposioHQ/composio typescript-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/typescript-testing .claude/skills/typescript-testing && rm -rf skills-srcUse ~/.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/
Install the "typescript-testing" agent skill from https://github.com/ComposioHQ/composio/tree/next/.agents/skills/typescript-testing into .claude/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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 install https://github.com/ComposioHQ/composio/tree/next/.agents/skills/typescript-testingType 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.
$ npx skills add ComposioHQ/composio --skill typescript-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ComposioHQ/composio typescript-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/typescript-testing .agents/skills/typescript-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "typescript-testing" agent skill from https://github.com/ComposioHQ/composio/tree/next/.agents/skills/typescript-testing into .agents/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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.
$ npx skills add ComposioHQ/composio --skill typescript-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ComposioHQ/composio typescript-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/typescript-testing .cursor/skills/typescript-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "typescript-testing" agent skill from https://github.com/ComposioHQ/composio/tree/next/.agents/skills/typescript-testing into .cursor/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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 https://github.com/ComposioHQ/composio.git --path .agents/skills/typescript-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ComposioHQ/composio --skill typescript-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ComposioHQ/composio typescript-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/typescript-testing .gemini/skills/typescript-testing && rm -rf skills-srcUse ~/.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/
Install the "typescript-testing" agent skill from https://github.com/ComposioHQ/composio/tree/next/.agents/skills/typescript-testing into .gemini/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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.
$ gh skill install ComposioHQ/composio typescript-testingInstalls 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).
$ npx skills add ComposioHQ/composio --skill typescript-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/typescript-testing .github/skills/typescript-testing && rm -rf skills-srcUse ~/.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/
Install the "typescript-testing" agent skill from https://github.com/ComposioHQ/composio/tree/next/.agents/skills/typescript-testing into .github/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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.
$ npx skills add ComposioHQ/composio --skill typescript-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ComposioHQ/composio typescript-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ComposioHQ/composio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/typescript-testing .opencode/skills/typescript-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "typescript-testing" agent skill from https://github.com/ComposioHQ/composio/tree/next/.agents/skills/typescript-testing into .opencode/skills/typescript-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "typescript-testing", 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
typescript-testing- GitHub stars
- 30k
- Token cost
- ~222 tokens
- SKILL.md length
- 49 words
- Files
- 3 (incl. references)
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests.
- Diagnosing TypeScript CI
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Choosing a focused test command
- Validating TypeScript package changes
What it does
Typescript Testing is an agent skill from ComposioHQ/composio. Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against effect@4.0.0-rc.117 and @effect/vitest. Do not use for Python-only checks.
Its SKILL.md is about 220 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/effect-v4-cli.md` and `references/test-commands.md`).
It sits in Testing & QA, covering Unit testing, Linting and formatting and End-to-end testing. It works with TypeScript, Python, Vitest and Model Context Protocol. The repository describes itself as: Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action. The licence is MIT.
When your agent uses it
- Diagnosing TypeScript CI
- Choosing a focused test command
- Validating TypeScript package changes
- Writing/porting CLI tests against effect@4.0.0-rc.117 and @effect/vitest
Example prompts
- “/typescript-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit 900bbb3. 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
Typescript Testing loads about 222 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 49 words of instructions outside code blocks.
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 ComposioHQ/composio at commit 900bbb3, republished under its MIT licence (© ComposioHQ). 49 words, ~222 tokens.
Download SKILL.mdSave it as
.claude/skills/typescript-testing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- typescript-testing
- description
- Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against effect@4.0.0-rc.117 and @effect/vitest. Do not use for Python-only checks.
TypeScript Testing
Use this skill to choose verification for TypeScript changes.
Read references/test-commands.md before running broad checks or adding new test coverage.
Read references/effect-v4-cli.md before writing or modifying tests under ts/packages/cli/test/
— it covers it.effect/layer(...) conventions, explicit per-service test layers (no .Default
auto-generation in v4), and the @effect/platform-bun subpath-import rule.
© ComposioHQ, 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 2 other files (references) in .agents/skills/typescript-testing of ComposioHQ/composio.
- SKILL.md
- references/effect-v4-cli.md
- references/test-commands.md
Open the folder on GitHubat commit 900bbb3
Compare with similar skills
Typescript Testing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Typescript Testing this skillComposioHQ/composio | 30k | — | ~222 | Automated safety check: Pass | MIT | |
| Ha Frontend Testinghome-assistant/frontend | 5.7k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Zizkadb TestZIZKA-AI-SL/ZizkaDB | 124 | — | ~358 | Automated safety check: Pass | Custom licence | |
| Testing Patternssoftspark/ai-toolkit | 179 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Svelte Testingspences10/sveltest | 113 | — | ~579 | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None |
Similar skills
Zizkadb Test
ZIZKA-AI-SL/ZizkaDB
Run the full ZizkaDB test suite across all layers — lint, Python unit tests, SDK tests, MCP tests, TypeScript tests, and dashboard build verification.
Testing Patterns
softspark/ai-toolkit
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage.
Svelte Testing
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Frontend Playwright E2E
ansible/ansible-ui
Write, run, and debug Playwright E2E / integration / live tests.
More from ComposioHQ/composio
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
Effect V4
ComposioHQ/composio
Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to effect@4.0.0-rc.117 — Context.Service and explicit layers…
CLI Release
ComposioHQ/composio
Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification…
Good Docs Audit
ComposioHQ/composio
Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations.
Good Docs Writing
ComposioHQ/composio
Writing style guide derived from Modal's documentation voice.
CLI Command
ComposioHQ/composio
Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, effect/unstable/cli, services, output conventions, configuration and environment variables, and local vendor…
Related
Categories
Questions about Typescript Testing
What does Typescript Testing do?
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Typescript Testing is an agent skill from ComposioHQ/composio. Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests.
When should I use Typescript Testing?
Typescript Testing fits situations like: diagnosing TypeScript CI; choosing a focused test command; validating TypeScript package changes; writing/porting CLI tests against effect@4.0.0-rc.117 and @effect/vitest.
How do I install Typescript Testing in Claude Code?
Run `npx skills add ComposioHQ/composio --skill typescript-testing -a claude-code`. Or copy the skill folder (.agents/skills/typescript-testing in ComposioHQ/composio) into .claude/skills/typescript-testing in your project. Claude Code loads it when a task matches its description.
How do I install Typescript Testing in Codex?
Run `npx skills add ComposioHQ/composio --skill typescript-testing -a codex`. Or copy the skill folder (.agents/skills/typescript-testing in ComposioHQ/composio) into .agents/skills/typescript-testing in your project. Codex loads it when a task matches its description.
Can I use Typescript Testing 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 ComposioHQ/composio --skill typescript-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/typescript-testing, .gemini/skills/typescript-testing, .github/skills/typescript-testing and .opencode/skills/typescript-testing in your project.
What does Typescript Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Typescript Testing is instructions for the agent only.
Does Typescript Testing 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 Typescript Testing 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 Typescript Testing use?
Typescript Testing 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 Typescript Testing use?
About 222 tokens (SKILL.md is roughly 888 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Typescript Testing?
Skills that share tags, products or a category with Typescript Testing: Ha Frontend Testing (home-assistant/frontend, 5.7k stars), Zizkadb Test (ZIZKA-AI-SL/ZizkaDB, 124 stars), Testing Patterns (softspark/ai-toolkit, 179 stars) and Svelte Testing (spences10/sveltest, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Typescript Testing?
ComposioHQ (a GitHub organization) maintains it in ComposioHQ/composio, which has 30,455 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: ComposioHQ/composio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.