Agent skill · Audited from source
coordinate-components
skill · dotnet/skillsMIT licenceAudited 14 Nov 2026 · source 75cbe55405f2
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 75cbe55405f2 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Share state between components that don't have a direct parent-child parameter relationship, using cascading values, scoped services with change events, or CascadingValueSource via DI. USE WHEN the user needs a…
Cite
Cite this page
ModelsAtlas. “coordinate-components (dotnet/skills)”. Retrieved 14 Nov 2026. https://modelsatlas.com/skills/dotnet/coordinate-components
Trust audit
Audit 0.4.1 · source read 14 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 75cbe55405f2 · 14 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherdotnet GitHub organizationOwner of the repository this skill is read from
- Source folderdotnet/skills/plugins/dotnet-blazor/skills/coordinate-componentsThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict75cbe55405f2A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Share state between components that don't have a direct parent-child parameter relationship, using cascading values, scoped services with change events, or CascadingValueSource via DI. USE WHEN the user needs a…
---
license: MIT
name: coordinate-components
description: >
Share state between components that don't have a direct parent-child parameter relationship,
using cascading values, scoped services with change events, or CascadingValueSource via DI.
USE WHEN the user needs a CascadingParameter or CascadingValue that works across render mode
boundaries, a shopping cart or notification count accessible from multiple pages, a theme or
user preference cascaded app-wide, or when components in different parts of the tree must
react when shared data changes. Also USE WHEN cascading values aren't reaching interactive
children in per-page interactivity mode, or when the user needs to understand scoped vs
singleton service lifetime for state on Blazor Server.
DO NOT USE for direct parent-child parameter passing or EventCallback (see author-component),
for persisting state across prerender-to-interactive transitions (see support-prerendering),
or for service abstractions for data fetching in Auto/WebAssembly (see fetch-and-send-data).
---
# Coordinate Components
## Step 1 — Read AGENTS.md
Read `AGENTS.md` at the workspace root to learn the project's conventions before making changes.
## Step 2 — Decide the scope
| Need | Mechanism | When to use |
|------|-----------|-------------|
| Subtree (same render mode) | `CascadingValue` component | Theme, layout config within a layout |
| App-wide (all render modes) | `CascadingValueSource<T>` via DI | Current user, feature flags, theme shared globally |
| Mutable shared state within a circuit | Scoped service + `Action` event | Shopping cart, notification count, selected filters |
For parent→child one level: use `[Parameter]` / `EventCallback` (see `author-component` skill).
For persisting state across prerender→interactive: see `support-prerendering` skill.
## Workflow (quick reference)
1. Choose the mechanism from the table in Step 2
2. If crossing render mode boundaries → use `CascadingValueSource<T>` (Step 4)
3. Register in `Program.cs` with `AddCascadingValue(...)` and `isFixed: false`
4. Consume via `[CascadingParameter]` in child components
5. Update via `NotifyChangedAsync(newValue)` — never page reload
6. For additional mutable state within a circuit → add scoped service (Step 5)
7. Wrap any `StateHasChanged` from background threads in `InvokeAsync`
8. Implement `IDisposable` — dispose timers, cancel tokens, unsubscribe events
## Step 3 — CascadingValue for subtree state
Wrap a subtree with `<CascadingValue>` to flow data to all descendants without passing it through every intermediate component.
```razor
@* In a layout or parent component *@
<CascadingValue Value="theme">
@Body
</CascadingValue>
@code {
private ThemeInfo theme = new() { ButtonClass = "btn-primary" };
}
```
Consume in any descendant:
```csharp
[CascadingParameter]
private ThemeInfo? Theme { get; set; }
```
**Rules:**
- Matched by **type**, not name. To cascade multiple values of the same type, add `Name`:
```razor
<CascadingValue Value="primary" Name="PrimaryTheme">...</CascadingValue>
```
```csharp
[CascadingParameter(Name = "PrimaryTheme")]
private ThemeInfo? Primary { get; set; }
```
- Set `IsFixed="true"` when the value never changes — avoids subscription overhead.
- **Does NOT cross render mode boundaries.** A `<CascadingValue>` in a static SSR parent is invisible to interactive children. See Step 6.
## Step 4 — CascadingValueSource<T> for app-wide state
Register a `CascadingValueSource<T>` in DI when the value must be available to **all components regardless of render mode**.
```csharp
// Program.cs
builder.Services.AddCascadingValue(sp =>
{
var theme = new ThemeInfo { ButtonClass = "btn-primary" };
return new CascadingValueSource<ThemeInfo>(theme, isFixed: false);
});
```
Consume identically to Step 3:
```csharp
[CascadingParameter]
private ThemeInfo? Theme { get; set; }
```
**To update and notify subscribers**, either mutate the existing object or replace it:
```razor
@* Component that changes the theme *@
@inject CascadingValueSource<ThemeInfo> ThemeSource
<button @onclick="ToggleDarkMode">Toggle theme</button>
@code {
private bool isDark;
private async Task ToggleDarkMode()
{
isDark = !isDark;
// Replace the value entirely:
var newTheme = new ThemeInfo { ButtonClass = isDark ? "btn-dark" : "btn-primary" };
await ThemeSource.NotifyChangedAsync(newTheme);
}
}
```
`NotifyChangedAsync()` (no argument) also works — mutate the object and then call it. `NotifyChangedAsync(newValue)` replaces the value and notifies in one step.
**Update protocol:** Whenever shared state changes, the component that changes it MUST inject `CascadingValueSource<T>` and call `NotifyChangedAsync()`. This is the only mechanism that triggers re-rendering in all `[CascadingParameter]` subscribers. Without this call, no subscribers update. Do not use `NavigationManager.Refresh()` or page reloads as a substitute.
**Rules:**
- `isFixed: false` enables change notifications. `isFixed: true` is better for truly static values (feature flags).
- **Crosses render mode boundaries** — works for per-page interactivity, global interactivity, and WebAssembly. Key advantage over `<CascadingValue>`.
- Keep cascaded types **granular**. Every `NotifyChangedAsync` re-renders ALL subscribers regardless of which property changed. Don't put all app state into one cascaded type.
- For Auto/WebAssembly apps, register in **both** server and `.Client` `Program.cs`. The type must be in a shared assembly.
## Step 5 — Scoped state service with change events
For mutable shared state that multiple components read **and write** (shopping cart, notification count, filters), use a scoped service with an event for change notification.
**Define the service:**
```csharp
public class CartState
{
private readonly List<CartItem> _items = [];
public IReadOnlyList<CartItem> Items => _items;
public intExcerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 75cbe55
git clone https://github.com/dotnet/skills git -C skills checkout 75cbe55405f2
The author documents no install command, so this uses the repository directly. Our verdict covers commit 75cbe55405f2 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
75cbe55405f2
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/dotnet/coordinate-components/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
anthropics/skills
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com),…
anthropics/skills
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.…
anthropics/skills
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design…
anthropics/skills
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual…
anthropics/skills
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or…
anthropics/skills
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users…
Add this badge to your README
[](https://modelsatlas.com/skills/dotnet/coordinate-components/)
<a href="https://modelsatlas.com/skills/dotnet/coordinate-components/"><img src="https://modelsatlas.com/skills/dotnet/coordinate-components/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about coordinate-components
What does the coordinate-components skill do?
Is coordinate-components safe to install?
What can coordinate-components access on my machine?
How current is this page?
Sources
- github.com/dotnet/skills/tree/main/plugins/dotnet-blazor/skills/ — the audited source at commit 75cbe55405f2 and every finding aboveObserved · 14 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the coordinate-components skill do?
- Is coordinate-components safe to install?
- What can coordinate-components access on my machine?