Skip to content
TrustedSkillsbeta
Back to all skills

Angular Testing

Checked
analogjs·vlatest·frontend·MIT

Helps with Angular, testing as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add analogjs/angular-skills --skill angular-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

analogjs

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned analogjs/angular-skills at 18996fd1b2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
18996fd1b2
Manifest
skills/angular-testing/SKILL.md
Scanned
1 file, 21 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The angular-testing skill enables AI agents to write and execute unit and integration tests for Angular applications. It supports testing components, services, directives, and more using frameworks like Jasmine and Karma.

When to use it

  • You need to verify the correctness of Angular component logic before deployment.
  • You're setting up a new Angular project and want to ensure testability from the start.
  • You are refactoring existing code and want automated tests to catch regressions.

Key capabilities

  • Writing unit tests for Angular components using TestBed
  • Mocking services and dependencies in tests
  • Running end-to-end (E2E) tests with Protractor or Cypress integration
  • Generating test scaffolding for new Angular features

Example prompts

  • "Write a unit test for the UserComponent that checks if the template renders correctly."
  • "Generate E2E tests for the login form in my Angular app using Cypress."
  • "Mock the AuthService and write a test case for the AuthGuard."

Tips & gotchas

  • Ensure your Angular project is set up with testing dependencies like Jasmine and Karma.
  • Test files should be placed in the src/testing directory or similar to avoid conflicts with production code.