New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Client Integration Authoring

by CommunityToolkit in CommunityToolkit/Aspire

Guides authoring and reviewing CommunityToolkit Aspire client integrations, including registration shape, configuration, keyed services, health checks, telemetry, READMEs, examples, and tests.

MITAuto-check passedDevelopment

Install Client Integration Authoring

skills CLI
$ npx skills add CommunityToolkit/Aspire --skill client-integration-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CommunityToolkit/Aspire client-integration-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/client-integration-authoring .claude/skills/client-integration-authoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
client-integration-authoring
GitHub stars
629
Token cost
~814 tokens
SKILL.md length
363 words
Files
3 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Guides authoring and reviewing CommunityToolkit Aspire client integrations, including registration shape, configuration, keyed services, health checks, telemetry, READMEs, examples, and tests.

  • Works in 4 steps: Client lifetime: singleton, scoped,… → Configuration source: connection string,… → Registration shape: default service,… → …
  • Tasks that involve Technical documentation
  • SKILL.md covers First step: classify the…, Authoring workflow, Non-negotiable conventions and Review workflow
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Client Integration Authoring is an agent skill from CommunityToolkit/Aspire. Guides authoring and reviewing CommunityToolkit Aspire client integrations, including registration shape, configuration, keyed services, health checks, telemetry, READMEs, examples, and tests.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/patterns.md` and `references/testing-and-documentation.md`).

It sits in Development, covering Technical documentation. The repository describes itself as: A community project with additional components and extensions for Aspire. The licence is MIT.

When your agent uses it

  • Tasks that involve Technical documentation

Example prompts

  • “Use the client-integration-authoring skill to guide authoring and reviewing CommunityToolkit Aspire client integrations, including registration…”
  • “/client-integration-authoring”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Client lifetime: singleton, scoped, transient, SDK-managed, or HttpClient-backed.
  2. Configuration source: connection string, configuration section, explicit settings, or a combination.
  3. Registration shape: default service, keyed service, custom service key, or a fluent builder.
  4. Optional concerns: health checks, tracing/metrics, Microsoft.Extensions.AI adapters, Native AOT, or multiple logical clients.

What it can do on your machine

Read from SKILL.md and the folder at commit 69a155d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Client Integration Authoring loads about 814 tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 363 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~814
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CommunityToolkit/Aspire at commit 69a155d, republished under its MIT licence (© CommunityToolkit). 363 words, ~814 tokens.

Download SKILL.mdSave it as .claude/skills/client-integration-authoring/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
client-integration-authoring
description
Guides authoring and reviewing CommunityToolkit Aspire client integrations, including registration shape, configuration, keyed services, health checks, telemetry, READMEs, examples, and tests.

Aspire client integration authoring

Use this skill when creating, modifying, or reviewing CommunityToolkit.Aspire.* client integration packages whose extension methods register consuming-application services.

First step: classify the integration

Inspect nearby client integrations and classify the requested work:

  1. Client lifetime: singleton, scoped, transient, SDK-managed, or HttpClient-backed.
  2. Configuration source: connection string, configuration section, explicit settings, or a combination.
  3. Registration shape: default service, keyed service, custom service key, or a fluent builder.
  4. Optional concerns: health checks, tracing/metrics, Microsoft.Extensions.AI adapters, Native AOT, or multiple logical clients.

Do not force every integration into one template. Read patterns and apply only the capabilities supported by the underlying client library and demonstrated by nearby integrations.

Authoring workflow

  1. Inspect two existing client integrations with the closest registration and configuration shape.
  2. Define the smallest public API that follows the underlying SDK and repository conventions.
  3. Implement settings binding, connection-string override, and the configuration callback in a predictable order.
  4. Add default and keyed registration only when both are useful and can behave consistently.
  5. Add health checks and telemetry only when the integration can implement them reliably.
  6. Add focused tests and documentation using testing and documentation.
  7. Add source, test, and example projects to CommunityToolkit.Aspire.slnx when new projects are created.
  8. Validate with the narrowest relevant build and test commands.
Show full SKILL.md (146 more words)Show less

Non-negotiable conventions

  • Client extension methods use the Microsoft.Extensions.Hosting namespace.
  • Client packages use CommunityToolkit.Aspire.[IntegrationName] naming and include the client package tag.
  • Public APIs require XML documentation.
  • Validate public inputs with the throw helpers used by nearby integrations.
  • Do not create or manually edit generated */api/*.cs files.
  • Fail with a clear configuration error when a client cannot be constructed unless an established integration pattern intentionally defers missing-configuration handling; do not silently create an invalid client.
  • Keep health checks lightweight and cancellation-aware.
  • Avoid adding health-check, telemetry, or HTTP dependencies when the integration does not use them.

Review workflow

Review for behavioral correctness rather than template conformity:

  • configuration precedence and missing-configuration behavior;
  • service lifetime and keyed/default symmetry;
  • duplicated registrations or health checks;
  • disposal and HttpClient usage;
  • telemetry opt-out behavior;
  • health-check names, timeouts, and failure handling;
  • README examples that match the actual API; and
  • tests that cover the supported registration shapes.

© CommunityToolkit, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/client-integration-authoring of CommunityToolkit/Aspire.

  • SKILL.md
  • references/patterns.md
  • references/testing-and-documentation.md

Open the folder on GitHubat commit 69a155d

Compare with similar skills

Client Integration Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Client Integration Authoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Client Integration Authoring this skillCommunityToolkit/Aspire629—~814Automated safety check: PassMIT
Diagram Designcathrynlavery/diagram-design44k1 repos~7.5kAutomated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
Get API Docs with chubandrewyng/context-hub14k2 repos~775Automated safety check: PassMIT
Doc SyncJetBrains/ideavim10k2 repos~2.6kAutomated safety check: PassMIT
Mailspring App ScreenshotsFoundry376/Mailspring18k—~1.4kAutomated safety check: PassGPL-3.0

Similar skills

  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    44k GitHub starsUsed in 1 repo~7.5k tokens
    DevelopmentAuto-check passed

  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed

  • Get API Docs with chub

    andrewyng/context-hub

    Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.

    14k GitHub starsUsed in 2 repos~775 tokens
    DevelopmentAuto-check passed

  • Doc Sync

    JetBrains/ideavim

    Official

    Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Mailspring App Screenshots

    Foundry376/Mailspring

    Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.

    18k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated 5 days ago
    DevelopmentAuto-check: notes

More from CommunityToolkit/Aspire

All 8 skills in this repo

  • Dotnet Inspect

    CommunityToolkit/Aspire

    Query .NET APIs across NuGet packages, platform libraries, and local files.

    629 GitHub starsUsed in 2 repos~1.5k tokens
    Auto-check passed

  • Aspire Monitoring

    CommunityToolkit/Aspire

    ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard.

    629 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Aspireify

    CommunityToolkit/Aspire

    WORKFLOW SKILL - Wire Aspire AppHosts or repair TypeScript AppHost toolchains.

    629 GitHub stars~5.3k tokensUpdated today
    Auto-check: notes

  • Aspire Deployment

    CommunityToolkit/Aspire

    WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.

    629 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes

  • Aspire Project V2 Migration

    CommunityToolkit/Aspire

    WORKFLOW SKILL - Safely migrates eligible Aspire 13.6+ AppHosts from legacy ProjectResource APIs to experimental DotnetProjectResource APIs after a per-resource assessment and explicit approval of…

    629 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Aspire Typescript Apphost

    CommunityToolkit/Aspire

    Generate a TypeScript AppHost from an existing C example AppHost, then add a TypeScriptAppHostTest-based integration test.

    629 GitHub stars~739 tokensUpdated today
    Auto-check passed

Categories

Questions about Client Integration Authoring

What does Client Integration Authoring do?

Guides authoring and reviewing CommunityToolkit Aspire client integrations, including registration shape, configuration, keyed services, health checks, telemetry, READMEs, examples, and tests. Client Integration Authoring is an agent skill from CommunityToolkit/Aspire. Guides authoring and reviewing CommunityToolkit Aspire client integrations, including registration shape, configuration, keyed services, health checks, telemetry, READMEs, examples, and tests.

When should I use Client Integration Authoring?

Client Integration Authoring fits situations like: tasks that involve Technical documentation.

How do I install Client Integration Authoring in Claude Code?

Run `npx skills add CommunityToolkit/Aspire --skill client-integration-authoring -a claude-code`. Or copy the skill folder (.agents/skills/client-integration-authoring in CommunityToolkit/Aspire) into .claude/skills/client-integration-authoring in your project. Claude Code loads it when a task matches its description.

How do I install Client Integration Authoring in Codex?

Run `npx skills add CommunityToolkit/Aspire --skill client-integration-authoring -a codex`. Or copy the skill folder (.agents/skills/client-integration-authoring in CommunityToolkit/Aspire) into .agents/skills/client-integration-authoring in your project. Codex loads it when a task matches its description.

Can I use Client Integration Authoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CommunityToolkit/Aspire --skill client-integration-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-integration-authoring, .gemini/skills/client-integration-authoring, .github/skills/client-integration-authoring and .opencode/skills/client-integration-authoring in your project.

What does Client Integration Authoring need to run?

SKILL.md names no scripts, command-line tools or credentials: Client Integration Authoring is instructions for the agent only.

Does Client Integration Authoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Client Integration Authoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Client Integration Authoring use?

Client Integration Authoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Client Integration Authoring use?

About 814 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 955 tokens, read only when the agent opens those files.

What are the alternatives to Client Integration Authoring?

Skills that share tags, products or a category with Client Integration Authoring: Diagram Design (cathrynlavery/diagram-design, 44k stars), Simple English (moeru-ai/airi, 50k stars), Get API Docs with chub (andrewyng/context-hub, 14k stars) and Doc Sync (JetBrains/ideavim, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Client Integration Authoring?

CommunityToolkit (a GitHub organization) maintains it in CommunityToolkit/Aspire, which has 629 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

Source: CommunityToolkit/Aspire on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.