[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EKF7FDMFJ4EMSTC0MFQP8H":3,"skill-same:01M7EKF7FDMFJ4EMSTC0MFQP8H":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M7EKF7FDMFJ4EMSTC0MFQP8H","coordinate-components",null,"> 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","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcloud\u002Fcoordinate-components\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: coordinate-components\ndescription: \"> 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\"\ncategory: cloud\nversion: 1.0.0\ndisable-model-invocation: false\nrisk: low\nsource:\n  repository: \"microsoft\u002Fskills\"\n  commit: \"8f3b1a2c\"\n  path: \"plugins\u002Fdotnet-blazor\u002Fskills\u002Fcoordinate-components\u002FSKILL.md\"\n  license: \"MIT\"\n  imported_at: \"2026-09-20\"\n---\n# Coordinate Components\n\n## Step 1 — Read AGENTS.md\n\nRead `AGENTS.md` at the workspace root to learn the project's conventions before making changes.\n\n## Step 2 — Decide the scope\n\n| Need | Mechanism | When to use |\n|------|-----------|-------------|\n| Subtree (same render mode) | `CascadingValue` component | Theme, layout config within a layout |\n| App-wide (all render modes) | `CascadingValueSource\u003CT>` via DI | Current user, feature flags, theme shared globally |\n| Mutable shared state within a circuit | Scoped service + `Action` event | Shopping cart, notification count, selected filters |\n\nFor parent→child one level: use `[Parameter]` \u002F `EventCallback` (see `author-component` skill).\nFor persisting state across prerender→interactive: see `support-prerendering` skill.\n\n## Workflow (quick reference)\n\n1. Choose the mechanism from the table in Step 2\n2. If crossing render mode boundaries → use `CascadingValueSource\u003CT>` (Step 4)\n3. Register in `Program.cs` with `AddCascadingValue(...)` and `isFixed: false`\n4. Consume via `[CascadingParameter]` in child components\n5. Update via `NotifyChangedAsync(newValue)` — never page reload\n6. For additional mutable state within a circuit → add scoped service (Step 5)\n7. Wrap any `StateHasChanged` from background threads in `InvokeAsync`\n8. Implement `IDisposable` — dispose timers, cancel tokens, unsubscribe events\n\n## Step 3 — CascadingValue for subtree state\n\nWrap a subtree with `\u003CCascadingValue>` to flow data to all descendants without passing it through every intermediate component.\n\n```razor\n@* In a layout or parent component *@\n\u003CCascadingValue Value=\"theme\">\n    @Body\n\u003C\u002FCascadingValue>\n\n@code {\n    private ThemeInfo theme = new() { ButtonClass = \"btn-primary\" };\n}\n```\n\nConsume in any descendant:\n\n```csharp\n[CascadingParameter]\nprivate ThemeInfo? Theme { get; set; }\n```\n\n**Rules:**\n- Matched by **type**, not name. To cascade multiple values of the same type, add `Name`:\n  ```razor\n  \u003CCascadingValue Value=\"primary\" Name=\"PrimaryTheme\">...\u003C\u002FCascadingValue>\n  ```\n  ```csharp\n  [CascadingParameter(Name = \"PrimaryTheme\")]\n  private ThemeInfo? Primary { get; set; }\n  ```\n- Set `IsFixed=\"true\"` when the value never changes — avoids subscription overhead.\n- **Does NOT cross render mode boundaries.** A `\u003CCascadingValue>` in a static SSR parent is invisible to interactive children. See Step 6.\n\n## Step 4 — CascadingValueSource&lt;T&gt; for app-wide state\n\nRegister a `CascadingValueSource\u003CT>` in DI when the value must be available to **all components regardless of render mode**.\n\n```csharp\n\u002F\u002F Program.cs\nbuilder.Services.AddCascadingValue(sp =>\n{\n    var theme = new ThemeInfo { ButtonClass = \"btn-primary\" };\n    return new CascadingValueSource\u003CThemeInfo>(theme, isFixed: false);\n});\n```\n\nConsume identically to Step 3:\n\n```csharp\n[CascadingParameter]\nprivate ThemeInfo? Theme { get; set; }\n```\n\n**To update and notify subscribers**, either mutate the existing object or replace it:\n\n```razor\n@* Component that changes the theme *@\n@inject CascadingValueSource\u003CThemeInfo> ThemeSource\n\n\u003Cbutton @onclick=\"ToggleDarkMode\">Toggle theme\u003C\u002Fbutton>\n\n@code {\n    private bool isDark;\n\n    private async Task ToggleDarkMode()\n    {\n        isDark = !isDark;\n        \u002F\u002F Replace the value entirely:\n        var newTheme = new ThemeInfo { ButtonClass = isDark ? \"btn-dark\" : \"btn-primary\" };\n        await ThemeSource.NotifyChangedAsync(newTheme);\n    }\n}\n```\n\n`NotifyChangedAsync()` (no argument) also works — mutate the object and then call it. `NotifyChangedAsync(newValue)` replaces the value and notifies in one step.\n\n**Update protocol:** Whenever shared state changes, the component that changes it MUST inject `CascadingValueSource\u003CT>` 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.\n\n**Rules:**\n- `isFixed: false` enables change notifications. `isFixed: true` is better for truly static values (feature flags).\n- **Crosses render mode boundaries** — works for per-page interactivity, global interactivity, and WebAssembly. Key advantage over `\u003CCascadingValue>`.\n- 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.\n- For Auto\u002FWebAssembly apps, register in **both** server and `.Client` `Program.cs`. The type must be in a shared assembly.\n\n## Step 5 — Scoped state service with change events\n\nFor mutable shared state that multiple components read **and write** (shopping cart, notification count, filters), use a scoped service with an event for change notification.\n\n**Define the service:**\n\n```csharp\npublic class CartState\n{\n    private readonly List\u003CCartItem> _items = [];\n\n    public IReadOnlyList\u003CCartItem> Items => _items;\n    public int Count => _items.Count;\n\n    public event Action? OnChange;\n\n    public void Add(CartItem item)\n    {\n        _items.Add(item);\n        OnChange?.Invoke();\n    }\n\n    public void Remove(CartItem item)\n    {\n        _items.Remove(item);\n        OnChange?.Invoke();\n    }\n}\n```\n\n**Register as scoped:**\n\n```csharp\nbuilder.Services.AddScoped\u003CCartState>();\n```\n\n**Subscribe in components:**\n\n```razor\n@inject CartState Cart\n@implements IDisposable\n\n\u003Cspan class=\"badge\">@Cart.Count\u003C\u002Fspan>\n\n@code {\n    protected override void OnInitialized()\n    {\n        Cart.OnChange += StateHasChanged;\n    }\n\n    public void Dispose()\n    {\n        Cart.OnChange -= StateHasChanged;\n    }\n}\n```\n\nThe simple `Action OnChange` pattern works when the event fires from the Blazor sync context (button click → `Cart.Add(…)`). If the event fires from **outside** the sync context (timer, background task, SignalR hub), wrap in `InvokeAsync`:\n\n```csharp\nprivate Action? _handler;\n\nprotected override void OnInitialized()\n{\n    _handler = () => InvokeAsync(StateHasChanged);\n    Cart.OnChange += _handler;\n}\n\npublic void Dispose() => Cart.OnChange -= _handler;\n```\n\nStore the delegate in a field so you can unsubscribe the exact same instance.\n\n## Step 6 — Render mode and service lifetime rules\n\n### Cascading values don't cross render mode boundaries\n\nA `\u003CCascadingValue>` placed in a static SSR layout (`MainLayout.razor` when the layout renders statically) will **not** reach interactive children. The interactive component sees `null` for the cascading parameter.\n\n**Fix:** Use `CascadingValueSource\u003CT>` registered in DI (Step 4) or a scoped service (Step 5). Both cross boundaries because DI services are resolved per-circuit, not from the component tree.\n\n### Service lifetime on Server vs WebAssembly\n\n| Lifetime | Server | WebAssembly |\n|----------|--------|-------------|\n| **Scoped** | Per circuit (per user connection) | Per browser tab |\n| **Singleton** | Shared across ALL users | Per browser tab (safe) |\n| **Transient** | New instance per injection | New instance per injection |\n\nOn Server, **never store user-specific state in a singleton** — every user's circuit shares the same singleton. One user's cart leaks into another's. Use `AddScoped\u003CT>()`.\n\nOn WebAssembly, singletons are per-tab and safe. But code meant for **both** Server and WebAssembly (Auto mode) must use scoped.\n\n### Auto\u002FWebAssembly with prerendering\n\nState services must be defined in the `.Client` project or a shared assembly — they cannot reference server-only types. Register the service in both `Program.cs` files. State created during prerender does not survive the switch to the interactive runtime. Use the `support-prerendering` skill's `[PersistentState]` pattern to carry state across.\n\n## Don'ts\n\n- **Don't use a singleton for per-user state on Server** — all circuits share it, leaking state between users.\n- **Don't put all app state into one cascaded object** — `NotifyChangedAsync` re-renders ALL subscribers on every change. Separate concerns into distinct types (`ThemeState`, `CartState`, `UserPreferences`).\n- **Don't forget to unsubscribe** — omitting `Dispose` on event subscriptions causes memory leaks that grow per-circuit.\n- **Don't use `\u003CCascadingValue>` in a static layout expecting it to reach interactive children** — it won't cross render mode boundaries. Use DI-registered `CascadingValueSource\u003CT>` or scoped services.\n- **Don't use `NavigationManager.Refresh(forceReload: true)` to propagate cascading value changes** — this destroys the circuit and forces a full page reload. Instead, inject `CascadingValueSource\u003CT>` and call `NotifyChangedAsync(newValue)` to push updates to all `[CascadingParameter]` subscribers without a page reload.\n- **Don't call `StateHasChanged` from a non-Blazor thread** — wrap in `InvokeAsync`. The framework throws `InvalidOperationException: The current thread is not associated with the Dispatcher`.\n","# Coordinate Components\n\n## Step 1 — Read AGENTS.md\n\nRead `AGENTS.md` at the workspace root to learn the project's conventions before making changes.\n\n## Step 2 — Decide the scope\n\n| Need | Mechanism | When to use |\n|------|-----------|-------------|\n| Subtree (same render mode) | `CascadingValue` component | Theme, layout config within a layout |\n| App-wide (all render modes) | `CascadingValueSource\u003CT>` via DI | Current user, feature flags, theme shared globally |\n| Mutable shared state within a circuit | Scoped service + `Action` event | Shopping cart, notification count, selected filters |\n\nFor parent→child one level: use `[Parameter]` \u002F `EventCallback` (see `author-component` skill).\nFor persisting state across prerender→interactive: see `support-prerendering` skill.\n\n## Workflow (quick reference)\n\n1. Choose the mechanism from the table in Step 2\n2. If crossing render mode boundaries → use `CascadingValueSource\u003CT>` (Step 4)\n3. Register in `Program.cs` with `AddCascadingValue(...)` and `isFixed: false`\n4. Consume via `[CascadingParameter]` in child components\n5. Update via `NotifyChangedAsync(newValue)` — never page reload\n6. For additional mutable state within a circuit → add scoped service (Step 5)\n7. Wrap any `StateHasChanged` from background threads in `InvokeAsync`\n8. Implement `IDisposable` — dispose timers, cancel tokens, unsubscribe events\n\n## Step 3 — CascadingValue for subtree state\n\nWrap a subtree with `\u003CCascadingValue>` to flow data to all descendants without passing it through every intermediate component.\n\n```razor\n@* In a layout or parent component *@\n\u003CCascadingValue Value=\"theme\">\n    @Body\n\u003C\u002FCascadingValue>\n\n@code {\n    private ThemeInfo theme = new() { ButtonClass = \"btn-primary\" };\n}\n```\n\nConsume in any descendant:\n\n```csharp\n[CascadingParameter]\nprivate ThemeInfo? Theme { get; set; }\n```\n\n**Rules:**\n- Matched by **type**, not name. To cascade multiple values of the same type, add `Name`:\n  ```razor\n  \u003CCascadingValue Value=\"primary\" Name=\"PrimaryTheme\">...\u003C\u002FCascadingValue>\n  ```\n  ```csharp\n  [CascadingParameter(Name = \"PrimaryTheme\")]\n  private ThemeInfo? Primary { get; set; }\n  ```\n- Set `IsFixed=\"true\"` when the value never changes — avoids subscription overhead.\n- **Does NOT cross render mode boundaries.** A `\u003CCascadingValue>` in a static SSR parent is invisible to interactive children. See Step 6.\n\n## Step 4 — CascadingValueSource&lt;T&gt; for app-wide state\n\nRegister a `CascadingValueSource\u003CT>` in DI when the value must be available to **all components regardless of render mode**.\n\n```csharp\n\u002F\u002F Program.cs\nbuilder.Services.AddCascadingValue(sp =>\n{\n    var theme = new ThemeInfo { ButtonClass = \"btn-primary\" };\n    return new CascadingValueSource\u003CThemeInfo>(theme, isFixed: false);\n});\n```\n\nConsume identically to Step 3:\n\n```csharp\n[CascadingParameter]\nprivate ThemeInfo? Theme { get; set; }\n```\n\n**To update and notify subscribers**, either mutate the existing object or replace it:\n\n```razor\n@* Component that changes the theme *@\n@inject CascadingValueSource\u003CThemeInfo> ThemeSource\n\n\u003Cbutton @onclick=\"ToggleDarkMode\">Toggle theme\u003C\u002Fbutton>\n\n@code {\n    private bool isDark;\n\n    private async Task ToggleDarkMode()\n    {\n        isDark = !isDark;\n        \u002F\u002F Replace the value entirely:\n        var newTheme = new ThemeInfo { ButtonClass = isDark ? \"btn-dark\" : \"btn-primary\" };\n        await ThemeSource.NotifyChangedAsync(newTheme);\n    }\n}\n```\n\n`NotifyChangedAsync()` (no argument) also works — mutate the object and then call it. `NotifyChangedAsync(newValue)` replaces the value and notifies in one step.\n\n**Update protocol:** Whenever shared state changes, the component that changes it MUST inject `CascadingValueSource\u003CT>` 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.\n\n**Rules:**\n- `isFixed: false` enables change notifications. `isFixed: true` is better for truly static values (feature flags).\n- **Crosses render mode boundaries** — works for per-page interactivity, global interactivity, and WebAssembly. Key advantage over `\u003CCascadingValue>`.\n- 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.\n- For Auto\u002FWebAssembly apps, register in **both** server and `.Client` `Program.cs`. The type must be in a shared assembly.\n\n## Step 5 — Scoped state service with change events\n\nFor mutable shared state that multiple components read **and write** (shopping cart, notification count, filters), use a scoped service with an event for change notification.\n\n**Define the service:**\n\n```csharp\npublic class CartState\n{\n    private readonly List\u003CCartItem> _items = [];\n\n    public IReadOnlyList\u003CCartItem> Items => _items;\n    public int Count => _items.Count;\n\n    public event Action? OnChange;\n\n    public void Add(CartItem item)\n    {\n        _items.Add(item);\n        OnChange?.Invoke();\n    }\n\n    public void Remove(CartItem item)\n    {\n        _items.Remove(item);\n        OnChange?.Invoke();\n    }\n}\n```\n\n**Register as scoped:**\n\n```csharp\nbuilder.Services.AddScoped\u003CCartState>();\n```\n\n**Subscribe in components:**\n\n```razor\n@inject CartState Cart\n@implements IDisposable\n\n\u003Cspan class=\"badge\">@Cart.Count\u003C\u002Fspan>\n\n@code {\n    protected override void OnInitialized()\n    {\n        Cart.OnChange += StateHasChanged;\n    }\n\n    public void Dispose()\n    {\n        Cart.OnChange -= StateHasChanged;\n    }\n}\n```\n\nThe simple `Action OnChange` pattern works when the event fires from the Blazor sync context (button click → `Cart.Add(…)`). If the event fires from **outside** the sync context (timer, background task, SignalR hub), wrap in `InvokeAsync`:\n\n```csharp\nprivate Action? _handler;\n\nprotected override void OnInitialized()\n{\n    _handler = () => InvokeAsync(StateHasChanged);\n    Cart.OnChange += _handler;\n}\n\npublic void Dispose() => Cart.OnChange -= _handler;\n```\n\nStore the delegate in a field so you can unsubscribe the exact same instance.\n\n## Step 6 — Render mode and service lifetime rules\n\n### Cascading values don't cross render mode boundaries\n\nA `\u003CCascadingValue>` placed in a static SSR layout (`MainLayout.razor` when the layout renders statically) will **not** reach interactive children. The interactive component sees `null` for the cascading parameter.\n\n**Fix:** Use `CascadingValueSource\u003CT>` registered in DI (Step 4) or a scoped service (Step 5). Both cross boundaries because DI services are resolved per-circuit, not from the component tree.\n\n### Service lifetime on Server vs WebAssembly\n\n| Lifetime | Server | WebAssembly |\n|----------|--------|-------------|\n| **Scoped** | Per circuit (per user connection) | Per browser tab |\n| **Singleton** | Shared across ALL users | Per browser tab (safe) |\n| **Transient** | New instance per injection | New instance per injection |\n\nOn Server, **never store user-specific state in a singleton** — every user's circuit shares the same singleton. One user's cart leaks into another's. Use `AddScoped\u003CT>()`.\n\nOn WebAssembly, singletons are per-tab and safe. But code meant for **both** Server and WebAssembly (Auto mode) must use scoped.\n\n### Auto\u002FWebAssembly with prerendering\n\nState services must be defined in the `.Client` project or a shared assembly — they cannot reference server-only types. Register the service in both `Program.cs` files. State created during prerender does not survive the switch to the interactive runtime. Use the `support-prerendering` skill's `[PersistentState]` pattern to carry state across.\n\n## Don'ts\n\n- **Don't use a singleton for per-user state on Server** — all circuits share it, leaking state between users.\n- **Don't put all app state into one cascaded object** — `NotifyChangedAsync` re-renders ALL subscribers on every change. Separate concerns into distinct types (`ThemeState`, `CartState`, `UserPreferences`).\n- **Don't forget to unsubscribe** — omitting `Dispose` on event subscriptions causes memory leaks that grow per-circuit.\n- **Don't use `\u003CCascadingValue>` in a static layout expecting it to reach interactive children** — it won't cross render mode boundaries. Use DI-registered `CascadingValueSource\u003CT>` or scoped services.\n- **Don't use `NavigationManager.Refresh(forceReload: true)` to propagate cascading value changes** — this destroys the circuit and forces a full page reload. Instead, inject `CascadingValueSource\u003CT>` and call `NotifyChangedAsync(newValue)` to push updates to all `[CascadingParameter]` subscribers without a page reload.\n- **Don't call `StateHasChanged` from a non-Blazor thread** — wrap in `InvokeAsync`. The framework throws `InvalidOperationException: The current thread is not associated with the Dispatcher`.\n",{"name":5,"risk":24,"source":25,"version":30,"category":31,"description":7,"disable-model-invocation":20},"low",{"path":26,"commit":27,"license":15,"repository":28,"imported_at":29},"plugins\u002Fdotnet-blazor\u002Fskills\u002Fcoordinate-components\u002FSKILL.md","8f3b1a2c","microsoft\u002Fskills","2026-09-20","1.0.0","cloud","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcloud\u002Fcoordinate-components","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill coordinate-components",{"tool":44,"command":45},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill coordinate-components",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill coordinate-components","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcloud\u002Fcoordinate-components\u002FSKILL.md",true,[],[53,61,68,75,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":60},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":60},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":60},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":60},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":60},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]