agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azuremonitor-opentelemetry-profiler-net/.github/skills/build-private-package/SKILL.md

build-private-package

Skill6 starsChanged 6 months agoMITView on GitHub

Build a private NuGet package for the Application Insights Profiler ASP.NET Core SDK. Use this skill when asked to build, pack, or create a private or test NuGet package for the profiler. Handles restore, build, uploader packing, and NuGet packaging.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user which package to build: if not specified:

    line 24
  2. Very specific:

    Ask the user which configuration to use if not specified.

    line 27
  3. Distinctive:

    Run the appropriate build script (see below).

    line 28
  4. Very specific:

    Check output for Package succeeded :-) to confirm success.

    line 29
  5. Distinctive:

    Run the build script:

    line 34
  6. Distinctive:

    Run the build script (requires PowerShell 7+):

    line 44
  7. Very specific:

    If PackUploader.cmd fails (Classic), check that the uploader projects build successfully.

    line 68
  8. Very specific:

    If NuGet pack fails with missing properties, verify NuspecProperties in the csproj include all variables referenced in the .nuspec files.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build Private Application Insights Profiler NuGet Package

Overview

This skill builds private NuGet packages for the Application Insights Profiler SDK. Two package flavors are available:

FlavorPackage(s)Script
Classic (ASP.NET Core / App Insights SDK)Microsoft.ApplicationInsights.Profiler.Core, Microsoft.ApplicationInsights.Profiler.AspNetCoresrc/ServiceProfiler.EventPipe/tools/PackNugetPackage.cmd
OTel (OpenTelemetry / Azure Monitor distro)Azure.Monitor.OpenTelemetry.Profilersrc/ServiceProfiler.EventPipe.Otel/tools/PackSolution.ps1

Steps

  1. Ask the user which package to build if not specified:
    • Classic (Application Insights Profiler ASP.NET Core)
    • OTel (Azure Monitor OpenTelemetry Profiler)
  2. Ask the user which configuration to use if not specified. Default to Debug.
  3. Run the appropriate build script (see below).
  4. Check output for Package succeeded :-) to confirm success.
  5. List the generated .nupkg files by running Get-ChildItem on the output directories. Report the actual full paths from the listing. Do NOT infer filenames from build log timestamps — OTel and Classic builds may have different timestamps even when built together.

Classic Package

Run the build script:

cmd /c "C:\AIR\fork-otel-profiler\src\ServiceProfiler.EventPipe\tools\PackNugetPackage.cmd <Config>"
  • First arg (required): Debug or Release
  • Second arg (optional): package type suffix, defaults to private
  • Third arg (optional): rebuild, TRUE (default) or FALSE

OTel Package

Run the build script (requires PowerShell 7+):

& "C:\AIR\fork-otel-profiler\src\ServiceProfiler.EventPipe.Otel\tools\PackSolution.ps1" -Configuration <Config>
  • -Configuration: Debug or Release (default: Release)
  • -PackageType: package type suffix (default: private)
  • -Rebuild: switch to force a rebuild
  • -VersionSuffix: optional custom version suffix

Output Locations

Classic

  • With symbols: src/ServiceProfiler.EventPipe/Out/Nuget/
  • Without symbols: src/ServiceProfiler.EventPipe/Out/NugetNoSymbols/

OTel

  • NuGet packages: Out/NuGets/

Version Format

99.YYYY.MMDD.HHmm-<packageType>YYMMDDHHMM

Troubleshooting

  • If PackUploader.cmd fails (Classic), check that the uploader projects build successfully.
  • If NuGet pack fails with missing properties, verify NuspecProperties in the csproj include all variables referenced in the .nuspec files.
  • OTel pack requires PowerShell 7+. Run pwsh --version to verify.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free