diagnose-project

diagnose-project is a skill for Claude Code, Codex from gaelic-ghost/socket. It costs 39 tokens per session (1,011 once invoked), scanned A, original, Apache-2.0.

A troubleshooting guide for .NET projects, including applications written in F# or C#. It helps identify the first meaningful cause of restore, build, test, package, SDK, and project-reference failures.

In plain words
What is it for?
Use it to investigate .NET SDK selection, package restore, target frameworks, F# file order, C# analyzers, and project-reference errors.
Why use it?
A message such as “build failed” often hides the actual problem. This guide narrows the failure to a command, project, and build stage before suggesting the smallest useful check.

Skill for Claude CodeCodex

Part of the dotnet-skills plugin — 12 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/gaelic-ghost/socket/diagnose-project
Any agent
npx skills add gaelic-ghost/socket --skill diagnose-project
Clone the repo
git clone --depth 1 https://github.com/gaelic-ghost/socket

Made for: Claude Code, Codex.

Or install dotnet-skills, the plugin that ships this one along with the rest of its 12 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for diagnose-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/gaelic-ghost/socket/diagnose-project.svg)](https://agentmods.dev/skills/gaelic-ghost/socket/diagnose-project)
Your own site
<a href="https://agentmods.dev/skills/gaelic-ghost/socket/diagnose-project"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/diagnose-project.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,011 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.01011
Opus 5 $0.00019 $0.00505
Sonnet 5 $0.00008 $0.00202
Haiku 4.5 $0.00004 $0.00101

Measured yesterday against content hash e9ac6f442e36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

diagnose-project scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/dotnet-skills/skills/diagnose-project/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Diagnose .NET Project

Purpose

Find the first meaningful cause of a .NET failure and explain it in human terms.

The useful answer is not "build failed." It is what command failed, which project failed, which phase failed, why it most likely failed, and the smallest next check or fix.

When To Use

  • Use this skill when dotnet restore, dotnet build, dotnet test, or dotnet pack fails.
  • Use this skill when SDK selection, target framework, package restore, or project references are unclear.
  • Use this skill when F# compile order or C# analyzer/nullability failures need explanation.
  • Use this skill before widening into refactors after a vague .NET error.

Source Check

Use repo-local .NET files, checked-out dependency sources, Dash MCP or Dash HTTP for installed .NET docsets, and then official Microsoft documentation when Dash/local coverage is missing or stale:

Diagnostic Workflow

  1. Capture repository shape:
    rg --files -g '*.sln' -g '*.slnx' -g '*.fsproj' -g '*.csproj' -g 'global.json' -g 'Directory.Build.props' -g 'Directory.Packages.props' -g 'NuGet.config'
    
  2. Check SDK context only when relevant:
    dotnet --info
    dotnet --list-sdks
    
  3. Re-run the narrowest failing command.
  4. Classify the failure phase:
    • SDK selection
    • restore
    • build
    • test discovery
    • test execution
    • pack
    • publish or release
  5. Identify the first meaningful error.
  6. Explain likely cause and next check.

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 112 lines · 39 tokens per session scan A e9ac6f442e36

Subscribe to this mod's changes

diagnose-project is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,011 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

pipeline

Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…

kardebadas/claude-plugin · 80 tokens

craft

Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…

kardebadas/claude-plugin · 83 tokens

chief-financial-officer

Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…

cbrock84/headcount · 88 tokens

chief-strategy-officer

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…

cbrock84/headcount · 93 tokens

business-growth-consultant

Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when…

cbrock84/headcount · 81 tokens

ceo-advisor

Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check…

cbrock84/headcount · 106 tokens