update-docs

update-docs is a skill for Claude Code, Codex from SAP/fundamental-ngx. It costs 17 tokens per session (688 once invoked), scanned A, original, Apache-2.0.

A documentation-checking command that compares examples and descriptions with a component's current public interface. A component is a reusable part of an application.

In plain words
What is it for?
Use it with a component or documentation path to check public inputs, outputs, models, descriptions, and example files.
Why use it?
It finds documentation that is missing, outdated, or inconsistent with the code, reducing confusion for users of the component.

Skill for Claude CodeCodex

About the project

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.

SAP/fundamental-ngx · 294 stars · on GitHub · sap.github.io

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/sap/fundamental-ngx/update-docs
Any agent
npx skills add SAP/fundamental-ngx --skill update-docs
Clone the repo
git clone --depth 1 https://github.com/SAP/fundamental-ngx

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for update-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/sap/fundamental-ngx/update-docs.svg)](https://agentmods.dev/skills/sap/fundamental-ngx/update-docs)
Your own site
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/update-docs"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/update-docs.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 688 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00688
Opus 5 $0.00009 $0.00344
Sonnet 5 $0.00003 $0.00138
Haiku 4.5 $0.00002 $0.00069

Measured 6d ago against content hash 43b1969b0f8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

update-docs 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 6d 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.

.claude/skills/update-docs/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Documentation: $ARGUMENTS

If $ARGUMENTS is empty, ask the user for a component path or folder before proceeding.

Verify that documentation examples are in sync with the component's current public API. If a path to a component is given, find its corresponding docs. If a docs path is given, find the component it documents.

Phase 1: Map component to docs

Component locations: libs/core/<component>/ or libs/platform/<component>/ Docs locations: libs/docs/core/<component>/ or libs/docs/platform/<component>/

Read:

  • The component .ts file — extract all input(), output(), model(), @Input(), @Output() declarations
  • The docs component (e.g. <component>-docs.component.ts and .html)
  • All example files in the docs examples/ folder

Phase 2: Audit

API coverage

For each public input/output/model on the component:

  • Is it demonstrated in at least one example?
  • Is it mentioned in a <description> block?
  • If it has non-obvious behavior, is there a dedicated section?

Flag inputs/outputs that exist in the component but are not documented anywhere.

Example quality

For each example file:

  • Individual component imports — no deprecated *Module classes
  • @fundamental-styles/common-css utility classes — no inline styles where avoidable
  • Every demonstrated feature is user-observable
  • No unnecessary standalone examples (consolidate where possible)
  • Example code matches current API (no removed/renamed inputs)

Description accuracy

For each <description> block in the docs HTML:

  • Input/output names in <code> tags match the actual component API
  • Described behavior matches the component's implementation
  • No references to removed or renamed APIs

Phase 3: Fix

For each issue found:

  1. Missing documentation — Add the input/output to an existing example's description, or add it to an existing example template if it can be demonstrated inline
  2. Stale references — Update <code> tags and descriptions to match current API
  3. Convention violations — Replace deprecated module imports, replace inline styles with common-css classes

Read the full file on GitHub · 91 lines

Changes

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.

  1. 6d ago First seen · 91 lines · 17 tokens per session scan A 43b1969b0f8c

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository SAP/fundamental-ngx (294 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 688 once invoked, about $0.0001 per session on Opus 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.

Related

Other skills, from other repositories

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.

anousss007/ng-blatui · 60 tokens

ng-blatui

Use the ng-blatui Angular UI library in an app — install, import components (bui-prefixed, signal-based, zoneless, SSR-safe), theme with Tailwind v4 + oklch tokens, localize dates/numbers/labels, and discover the full catalog via the registry, api.json, llms.txt or the ng-blatui-mcp MCP server. Invoke when building…

anousss007/ng-blatui · 108 tokens

neuralng-angular

Build or update Angular 22+ interfaces with NeuralNg when exact component selection, imports, forms, accessibility, SSR, icons, or theming guidance is needed.

hasanaydin7/NeuralTech · 38 tokens

igniteui-angular-figma-to-app

Translate Figma app screens designed using the Indigo.Design UI Kits into production Angular applications with Ignite UI for Angular. The Indigo.Design UI Kits are Figma component libraries available in four design-system variants — Material, Fluent, Bootstrap, and Indigo — each with light and dark themes. Designers…

IgniteUI/igniteui-angular · 210 tokens

igniteui-angular-generate-from-image-design

Implement Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built…

IgniteUI/igniteui-angular · 124 tokens

igniteui-angular-theming

Generates and customizes Ignite UI for Angular themes including color palettes, typography, elevations, and component-level styles using the Sass theming system and the igniteui-theming MCP server. Use when users ask to theme, restyle, or style Ignite UI components, change colors or the color palette, switch between…

IgniteUI/igniteui-angular · 130 tokens