New: 98,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

Profiling

by managedcode in managedcode/dotnet-skills

Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories.

MITAuto-check passedAgent Workflows

Install Profiling

skills CLI
$ npx skills add managedcode/dotnet-skills --skill profiling -a claude-code

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

GitHub CLI
$ gh skill install managedcode/dotnet-skills profiling --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/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/Profiling/skills/profiling .claude/skills/profiling && 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
profiling
GitHub stars
486
Token cost
~1.6k tokens
SKILL.md length
712 words
Files
5 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • : the repo needs performance
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 8 more sections
  • Calls dotnet

What it does

Profiling is an agent skill from managedcode/dotnet-skills. Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. USE FOR: the repo needs performance or runtime profiling for a .NET application; the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock. DO NOT USE FOR: replacing realistic performance tests or load tests with ad-hoc tracing alone; production heap collection when the pause risk has not been. INVOKES: inspect the repository context, edit targeted files, and run…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `manifest.json`, `references/commands.md` and `references/patterns.md`). Compatibility notes: Requires a .NET app or process to inspect; respects the repo's AGENTS.md commands first.

It sits in Agent Workflows, covering Load testing and Codebase knowledge for agents. It works with .NET. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : the repo needs performance
  • Runtime profiling for a .NET application
  • The user asks about slow code
  • Allocation growth

Example prompts

  • “/profiling”

Requirements

  • Compatibility (from SKILL.md): Requires a .NET app or process to inspect; respects the repo's `AGENTS.md` commands first.

Workflow steps

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

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. 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

    Shell commands in SKILL.md call:

    • dotnet

    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.

  • Compatibility

    Requires a .NET app or process to inspect; respects the repo's `AGENTS.md` commands first.

    From compatibility in the SKILL.md frontmatter.

Context cost

Profiling loads about 1.6k tokens when it runs, and up to ~8.5k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 712 words of instructions outside code blocks.

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

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 managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 712 words, ~1,573 tokens.

Download SKILL.mdSave it as .claude/skills/profiling/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
profiling
description
Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. USE FOR: the repo needs performance or runtime profiling for a .NET application; the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock. DO NOT USE FOR: replacing realistic performance tests or load tests with ad-hoc tracing alone; production heap collection when the pause risk has not been. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires a .NET app or process to inspect; respects the repo's `AGENTS.md` commands first.

.NET Profiling

Trigger On

  • the repo needs performance or runtime profiling for a .NET application
  • the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock contention, or startup diagnostics
  • the team wants official CLI-based diagnostics without depending on dnx

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • replacing realistic performance tests or load tests with ad-hoc tracing alone
  • production heap collection when the pause risk has not been accepted
  • GUI-only workflows that the repo cannot automate or document

Inputs

  • the nearest AGENTS.md
  • target application, process, or startup path
  • the symptom being investigated: CPU, memory, GC, contention, exceptions, or startup

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Build and run a realistic target first:
    • prefer Release
    • prefer realistic config, inputs, and data volume
  2. Start with the lightest useful tool:
    • dotnet-counters for live health signals
    • dotnet-trace for CPU, exception, contention, GC, and startup traces
    • dotnet-gcdump for managed heap inspection when memory shape matters
  3. Prefer installed CLI tools over dnx one-shot execution so the repo commands stay stable and reproducible.
  4. Capture one focused profile at a time instead of mixing every signal into one run.
  5. For CPU and general runtime hotspots, start with dotnet-trace collect.
  6. For live triage, start with dotnet-counters monitor on System.Runtime.
  7. For heap analysis, use dotnet-gcdump carefully and document the pause risk.
  8. After each change, rerun the same measurement path and compare before versus after.

Bootstrap When Missing

If official .NET profiling tools are not available yet:

  1. Detect current state:
    • dotnet --info
    • dotnet tool list --global
    • command -v dotnet-counters
    • command -v dotnet-trace
    • command -v dotnet-gcdump
  2. Choose the install path deliberately:
    • preferred machine-level install:
      • dotnet tool install --global dotnet-counters
      • dotnet tool install --global dotnet-trace
      • dotnet tool install --global dotnet-gcdump
    • direct-download fallback when global tools are not suitable:
      • use the official Microsoft Learn download links for dotnet-counters, dotnet-trace, and dotnet-gcdump
  3. Verify the installed tools resolve correctly:
    • dotnet-counters --version
    • dotnet-trace --version
    • dotnet-gcdump --version
  4. Record exact profiling commands in AGENTS.md, for example:
    • dotnet-counters monitor --process-id PID --counters System.Runtime
    • dotnet-trace collect --process-id PID --profile dotnet-common,dotnet-sampled-thread-time -o trace.nettrace
    • dotnet-gcdump collect --process-id PID --output heap.gcdump
  5. Run one bounded command and return status: configured or status: improved.
  6. If the repo intentionally standardizes on another profiling stack and does not want these tools, return status: not_applicable.
Show full SKILL.md (264 more words)Show less

Deliver

  • explicit official .NET profiling commands
  • a clear profiling path for CPU, counters, and heap inspection
  • reproducible diagnostics commands that humans and agents can rerun

Validate

  • the chosen tool matches the actual symptom
  • commands target a realistic process and configuration
  • before/after comparisons use the same scenario
  • heap collection warnings are explicit when dotnet-gcdump is used

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Plan first (mandatory):
    • analyze current state
    • define target outcome, constraints, and risks
    • write a detailed execution plan
    • list final validation skills to run at the end, with order and reason
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

Example Requests

  • "Profile this .NET app for CPU hotspots."
  • "Investigate GC pressure in this service."
  • "Capture counters and a trace from startup."
  • "Set up official .NET profiling tools for local investigations."

© managedcode, 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 4 other files (references) in catalog/Tools/Profiling/skills/profiling of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/commands.md
  • references/patterns.md
  • references/profiling.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

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

Profiling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Profiling this skillmanagedcode/dotnet-skills486—~1.6kAutomated safety check: PassMIT
Code Reviewdotnet/macios2.9k—~1.7kAutomated safety check: PassCustom licence
ccc Semantic Code Searchcocoindex-io/cocoindex-code2.7k—~938Automated safety check: PassApache-2.0
Repomix Codebase Packeryamadashy/repomix29k—~1.3kAutomated safety check: NotesMIT
Microbenchmarkingdotnet/skills5.6k3 repos~3.3kAutomated safety check: PassMIT
Codebase Handbook BuilderRuhan-Wang/Harness_Handbook332—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • Code Review

    dotnet/macios

    Official

    Review dotnet/macios PRs against established rules. An agent skill from dotnet/macios.

    2.9k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • ccc Semantic Code Search

    cocoindex-io/cocoindex-code

    Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.

    2.7k GitHub stars~938 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Repomix Codebase Packer

    yamadashy/repomix

    Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.

    29k GitHub stars~1.3k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check: notes

  • Microbenchmarking

    dotnet/skills

    Official

    Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks.

    5.6k GitHub starsUsed in 3 repos~3.3k tokens
    Testing & QAAuto-check passed

  • Codebase Handbook Builder

    Ruhan-Wang/Harness_Handbook

    Generates, refreshes, validates and uses a compact handbook that maps where a change touches in a repository, using the active Codex session and no external LLM API.

    332 GitHub stars~2.2k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Codemap

    JordanCoin/codemap

    Gives an agent a quick map of a codebase's structure, dependencies, changes and handoffs, and tunes per-project config so the output stays code-first.

    704 GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Profiling

What does Profiling do?

Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. Profiling is an agent skill from managedcode/dotnet-skills.NET repositories.

When should I use Profiling?

Profiling fits situations like: : the repo needs performance; runtime profiling for a .NET application; the user asks about slow code; allocation growth.

How do I install Profiling in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill profiling -a claude-code`. Or copy the skill folder (catalog/Tools/Profiling/skills/profiling in managedcode/dotnet-skills) into .claude/skills/profiling in your project. Claude Code loads it when a task matches its description.

How do I install Profiling in Codex?

Run `npx skills add managedcode/dotnet-skills --skill profiling -a codex`. Or copy the skill folder (catalog/Tools/Profiling/skills/profiling in managedcode/dotnet-skills) into .agents/skills/profiling in your project. Codex loads it when a task matches its description.

Can I use Profiling 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 managedcode/dotnet-skills --skill profiling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/profiling, .gemini/skills/profiling, .github/skills/profiling and .opencode/skills/profiling in your project.

What does Profiling need to run?

Going by SKILL.md and its folder, Profiling needs the command-line tools its instructions call (dotnet). Compatibility (from SKILL.md): Requires a .NET app or process to inspect; respects the repo's `AGENTS.md` commands first..

Does Profiling 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 Profiling 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 Profiling use?

Profiling 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 Profiling use?

About 1.6k tokens (SKILL.md is roughly 6.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 6.9k tokens, read only when the agent opens those files.

What are the alternatives to Profiling?

Skills that share tags, products or a category with Profiling: Code Review (dotnet/macios, 2.9k stars), ccc Semantic Code Search (cocoindex-io/cocoindex-code, 2.7k stars), Repomix Codebase Packer (yamadashy/repomix, 29k stars) and Microbenchmarking (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Profiling?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

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