Borrowing it
Nothing to install: this file belongs to rodydavis/signals.dart. 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/rodydavis/signals.dart/main/.agents/skills/update-docs-workflow/SKILL.mdgit clone --depth 1 https://github.com/rodydavis/signals.dartWrote 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/rodydavis/signals.dart/update-docs-workflow)<a href="https://agentmods.dev/skills/rodydavis/signals.dart/update-docs-workflow"><img src="https://agentmods.dev/badge/skills/rodydavis/signals.dart/update-docs-workflow.svg" alt="Measured on agentmods" height="20"></a>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.00034 | $0.00713 |
| Opus 5 | $0.00017 | $0.00357 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
update-docs-workflow 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jaspr Documentation Audit and Regeneration Workflow
This skill provides a systematic and automated workflow to inspect generated Jaspr reference files, trace documentation back to its source Dart declarations, audit comments for completeness, enrich source comments with examples, and run the doc generator to verify static site updates.
Objective
Ensure all public APIs across the monorepo have high-quality, comprehensive documentation comments (///) with functional usage examples and clean styling without placeholders.
[!IMPORTANT] Focus exclusively on the
docs/directory and Jaspr documentation site. Completely ignore thewebsite/directory (which contains the legacy/alternative Astro configuration).
🛠️ Step-by-Step Workflow
Step 1. Review Generated Markdown Docs
Locate the generated reference markdown files under the Jaspr docs tree:
docs/content/packages/
For example, check if specific pages under preact_signals/, signals_core/, or signals_flutter/ are minimal, outdated, or contain empty blocks.
Step 2. Trace to Source Declarations
Use the declaration name and package context from the markdown file to locate the corresponding source file under the package’s source tree:
- preact_signals:
packages/preact_signals/lib/src/ - signals_core:
packages/signals_core/lib/src/ - signals_flutter:
packages/signals_flutter/lib/src/ - signals_hooks:
packages/signals_hooks/lib/src/
Step 3. Run the Programmatic Doc Comment Auditor
Execute the programmatic audit script to check for declarations lacking comments or examples:
dart /Users/rodydavis/.gemini/antigravity/brain/5f607010-d7ba-40da-b166-4b3c433388c9/scratch/analyze_doc_comments.dart
Step 4. Enrich Dart Source Code Comments
Open the target source file and enrich the /// comments on classes, functions, and extensions using the following standards:
- Comprehensive Explanations: Explain the reactive behavior, lazy calculation, memoization caching, or event subscription behaviors.
- Comparative Code Examples: Show sequential vs batched updating behaviors (like in
action.dart), or standard vs custom equality logic. - XML-Style Callouts: Use
<Info>,<Warning>,<Error>, or<Success>XML tags inside comments rather than markdown triple-colon syntax (:::) to leverage Jaspr's custom callout components.
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.
- 8d ago First seen · 66 lines · 34 tokens per session scan A 53a1f5d17ab5
update-docs-workflow is a skill published in the GitHub repository rodydavis/signals.dart (813 stars, last pushed 21d ago), licensed Apache-2.0. It adds 34 tokens to every session and 713 once invoked, about $0.0002 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.
Other skills, from other repositories
flutter-expert
Expert in Flutter SDK, Dart, widgets, state management, and cross-platform mobile development. Use when the user mentions mobile, Dart, cross platform, UI, or state management, or when the task involves Flutter Architecture, Widget Fundamentals, State Management Approaches, or Lifecycle Methods.
flutter
Flutter 3.44 — widget catalog, layouts, interactivity, animations, navigation, assets, adaptive/responsive design, accessibility, i18n, state management, data & backend (networking, serialization, Firebase, persistence), app architecture (MVVM, DI), platform integration (Android, iOS, web, Windows, macOS, Linux…
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).