Fundamental Library for Angular is an SAP-maintained Angular component library implementing SAP's design system and wrapping UI5 Web Components. Angular developers use its typed UI components and higher-level composites to build SAP-style web interfaces. Catalogue entries provide skills, agents, instructions, and a rule for working with the library.
Borrowing it
Nothing to install: this file belongs to SAP/fundamental-ngx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAP/fundamental-ngx/main/.claude/skills/create-test/SKILL.mdgit clone --depth 1 https://github.com/SAP/fundamental-ngxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sap/fundamental-ngx/create-test)<a href="https://agentmods.dev/skills/sap/fundamental-ngx/create-test"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/create-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/create-test"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/create-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00015 | $0.00605 |
| Opus 5.5 | $0.00006 | $0.00242 |
| Sonnet 5.5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
create-test scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create/Update Tests: $ARGUMENTS
If $ARGUMENTS is empty, ask the user for a component path before proceeding.
Phase 1: Analyze the component
Read the component file at $ARGUMENTS. Extract:
- All
input()/input.required()and@Input()declarations with types and defaults - All
output()and@Output()declarations with event types - All
model()declarations - All public/protected methods
- Template interactions (click handlers, form bindings, conditional rendering)
- Host bindings and listeners
- Injected dependencies
Phase 2: Check existing tests
Look for an existing .spec.ts file alongside the component. If found, read it and identify:
- What is already covered
- What is missing based on the component analysis
- Any patterns that violate project conventions (see below)
Phase 3: Generate/update tests
Conventions to follow
Structure:
- One
describeblock per component - Nested
describefor each feature group (inputs, outputs, interactions, a11y) itdescriptions should be user-focused: "should display label when label input is set"- AAA pattern: Arrange → Act → Assert
Signal inputs:
- Use
fixture.componentRef.setInput('inputName', value)— never assign directly - Call
fixture.detectChanges()after setting inputs - Test default values by checking initial render without setting input
Imports:
- Individual component/directive imports — no deprecated
*Moduleclasses - Import only what the test needs
Test components:
- Use unique names:
MenuTestComponent, notTestComponent - Keep test component templates minimal — only what's needed for the test
What to test:
- Default rendering
- Each input affects the component as expected
- Outputs emit correct events on user interaction
- Two-way bindings (
model()) update in both directions - Keyboard navigation where applicable
- Disabled state behavior
- Edge cases: empty strings, null values, boundary numbers
What NOT to test:
- TypeScript-prevented scenarios (passing wrong types)
- Angular DI-prevented scenarios (missing required providers)
- Private methods or internal signal values
- Implementation details (internal CSS classes unless they're the public API)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 89 lines · 15 tokens per session scan A a419863c6e89
create-test is a skill published in the GitHub repository SAP/fundamental-ngx (296 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 605 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
igniteui-angular-testing
Quick-reference for running Ignite UI for Angular test suites. Covers the full library run (test:lib) on Vitest browser mode through the Angular unit-test builder, running a subset with --include/--filter, watch mode, extras/elements suites, and auxiliary suites (schematics, styles, i18n). WHEN TO USE: running…
angular-best-practices
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
authoring-benchmarks
Design, implement, run, debug, and interpret browser performance benchmarks for Elements components and utilities. Use whenever the user asks to benchmark or performance-test runtime code, create or update a .test.bench.ts file, compare benchmark results, investigate a browser performance regression, understand Vitest…
agent-starters
Verify every starter supported by the stable production NVIDIA Elements CLI from a fresh consumer environment, investigate failures, and prepare at most one focused repair pull request. Use for nightly or scheduled production starter verification and starter availability failures.
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…