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

Binlog Failure Analysis

by rodri-oliveira-dev in rodri-oliveira-dev/Dapper-FluentMap

Analyze MSBuild binary logs to diagnose build failures. An agent skill from rodri-oliveira-dev/Dapper-FluentMap.

MITAuto-check passedDevelopment

Install Binlog Failure Analysis

skills CLI
$ npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill binlog-failure-analysis -a claude-code

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

GitHub CLI
$ gh skill install rodri-oliveira-dev/Dapper-FluentMap binlog-failure-analysis --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/rodri-oliveira-dev/Dapper-FluentMap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/binlog-failure-analysis .claude/skills/binlog-failure-analysis && 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
binlog-failure-analysis
GitHub stars
453
Token cost
~750 tokens
SKILL.md length
248 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Analyze MSBuild binary logs to diagnose build failures. An agent skill from rodri-oliveira-dev/Dapper-FluentMap.

  • : unclear MSBuild errors
  • SKILL.md covers Preferred path — structured…, Fallback — replay binary log…, Generating a binlog when needed and Repository-specific checks, plus 1 more section
  • Calls dotnet
  • Cascading failures across the multi-project solution

What it does

Binlog Failure Analysis is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Analyze MSBuild binary logs to diagnose build failures. USE FOR: unclear MSBuild errors, cascading failures across the multi-project solution, tracing target execution/order, and inspecting evaluated properties/items. Requires an existing .binlog or explicit permission to generate one. DO NOT USE FOR: non-MSBuild build systems.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Root cause analysis. The repository describes itself as: Fluent mapping for Dapper, with conventions, immutable object materialization, analyzers, source generators, DI integration, and Dommel support. The licence is MIT.

When your agent uses it

  • : unclear MSBuild errors
  • Cascading failures across the multi-project solution
  • Tracing target execution/order
  • Inspecting evaluated properties/items

Example prompts

  • “/binlog-failure-analysis”

What it can do on your machine

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

Context cost

Binlog Failure Analysis loads about 750 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 248 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~750

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 rodri-oliveira-dev/Dapper-FluentMap at commit 90600cb, republished under its MIT licence (© rodri-oliveira-dev). 248 words, ~750 tokens.

Download SKILL.mdSave it as .claude/skills/binlog-failure-analysis/SKILL.md (or your agent's skills folder).
name
binlog-failure-analysis
description
Analyze MSBuild binary logs to diagnose build failures. USE FOR: unclear MSBuild errors, cascading failures across the multi-project solution, tracing target execution/order, and inspecting evaluated properties/items. Requires an existing .binlog or explicit permission to generate one. DO NOT USE FOR: non-MSBuild build systems.
license
MIT

Analyzing MSBuild Failures with Binary Logs

This skill diagnoses MSBuild failures from .binlog evidence.

Dapper-FluentMap integration: prefer the narrowest failing project or Dapper.FluentMap.slnx command. Consider root Directory.Build.props, Directory.Build.targets, project-specific package versions, analyzer/generator projects, pack targets, and compatibility validation when tracing failures. A binlog-aware MCP/tool is optional, not assumed. Do not attempt to read .binlog as plain text.

Preferred path — structured binlog tooling when available

If a binlog-aware tool is available, inspect:

  • errors and warnings;
  • evaluated MSBuild properties;
  • PackageReference and ProjectReference items;
  • project evaluation data;
  • target execution/order;
  • the first causal failure before cascaded project failures.

Stop once the cause and affected target/property chain are sufficiently established.

Fallback — replay binary log to focused text logs

bash
dotnet msbuild build.binlog -noconlog \
  -fl  -flp:v=diag\;logfile=full.log\;performancesummary \
  -fl1 -flp1:errorsonly\;logfile=errors.log \
  -fl2 -flp2:warningsonly\;logfile=warnings.log

PowerShell requires appropriate quoting around semicolon-delimited logger parameters.

Then search generated text logs, not the binary file:

bash
cat errors.log
grep -n -B2 -A2 "CS0246" full.log
grep -i "CoreCompile.*FAILED\|Build FAILED\|error MSB" full.log

Generating a binlog when needed

If no binlog exists and the task requires one:

bash
dotnet build ./Dapper.FluentMap.slnx --configuration Release /bl:build.binlog

Prefer a narrower failing .csproj command when it reproduces the issue. Treat .binlog and replay logs as temporary diagnostic artifacts unless explicitly requested otherwise.

Repository-specific checks

When the failure involves packaging/release, correlate the binlog with:

  • Directory.Build.props / Directory.Build.targets;
  • eng/package-catalog.json;
  • package validation targets/scripts;
  • analyzer/generator project settings;
  • netstandard2.0 compatibility constraints;
  • explicit package-version properties/PackageReference values.

Validation

  • Cause is supported by properties/items/targets from the log rather than guessed from the final console error
  • Cascading errors are distinguished from the first causal failure
  • No binary log was parsed with plain-text tools
  • Temporary diagnostic artifacts are not committed
  • Fix is validated with the repository's deterministic build/test and pack checks when relevant

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

Files

Just SKILL.md in .agents/skills/binlog-failure-analysis of rodri-oliveira-dev/Dapper-FluentMap.

Open the folder on GitHubat commit 90600cb

Compare with similar skills

Binlog Failure Analysis 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.

Binlog Failure Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Binlog Failure Analysis this skillrodri-oliveira-dev/Dapper-FluentMap453—~750Automated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Review PRapache/shardingsphere21k—~6.4kAutomated safety check: PassApache-2.0

Similar skills

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

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

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Review PR

    apache/shardingsphere

    Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.

    21k GitHub stars~6.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed

More from rodri-oliveira-dev/Dapper-FluentMap

All 11 skills in this repo

  • Directory Build Organization

    rodri-oliveira-dev/Dapper-FluentMap

    Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props when present, and related repository build files.

    453 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed

  • Microbenchmarking

    rodri-oliveira-dev/Dapper-FluentMap

    Activate when BenchmarkDotNet is involved or when a .NET performance question requires controlled microbenchmark measurement.

    453 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Nuget Trusted Publishing

    rodri-oliveira-dev/Dapper-FluentMap

    Review, maintain, or set up NuGet trusted publishing (OIDC) for GitHub Actions.

    453 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Test Gap Analysis

    rodri-oliveira-dev/Dapper-FluentMap

    Pseudo-mutation analysis for behavioral blind spots: determine whether existing tests would catch meaningful caller-visible production changes, identify survivors or untested outcomes, and…

    453 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

  • Authoring GitHub Workflows

    rodri-oliveira-dev/Dapper-FluentMap

    Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.

    453 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • CI Release Governance

    rodri-oliveira-dev/Dapper-FluentMap

    A skill your agent uses to review or adjust Dapper-FluentMap GitHub Actions, packaging, NuGet publishing, versioning, release, rollback, recovery, provenance, and automation security.

    453 GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Binlog Failure Analysis

What does Binlog Failure Analysis do?

Analyze MSBuild binary logs to diagnose build failures. An agent skill from rodri-oliveira-dev/Dapper-FluentMap. Binlog Failure Analysis is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Analyze MSBuild binary logs to diagnose build failures.

When should I use Binlog Failure Analysis?

Binlog Failure Analysis fits situations like: : unclear MSBuild errors; cascading failures across the multi-project solution; tracing target execution/order; inspecting evaluated properties/items.

How do I install Binlog Failure Analysis in Claude Code?

Run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill binlog-failure-analysis -a claude-code`. Or copy the skill folder (.agents/skills/binlog-failure-analysis in rodri-oliveira-dev/Dapper-FluentMap) into .claude/skills/binlog-failure-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Binlog Failure Analysis in Codex?

Run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill binlog-failure-analysis -a codex`. Or copy the skill folder (.agents/skills/binlog-failure-analysis in rodri-oliveira-dev/Dapper-FluentMap) into .agents/skills/binlog-failure-analysis in your project. Codex loads it when a task matches its description.

Can I use Binlog Failure Analysis 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 rodri-oliveira-dev/Dapper-FluentMap --skill binlog-failure-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/binlog-failure-analysis, .gemini/skills/binlog-failure-analysis, .github/skills/binlog-failure-analysis and .opencode/skills/binlog-failure-analysis in your project.

What does Binlog Failure Analysis need to run?

Going by SKILL.md and its folder, Binlog Failure Analysis needs the command-line tools its instructions call (dotnet).

Does Binlog Failure Analysis 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 Binlog Failure Analysis 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 Binlog Failure Analysis use?

Binlog Failure Analysis is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Binlog Failure Analysis use?

About 750 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Binlog Failure Analysis?

Skills that share tags, products or a category with Binlog Failure Analysis: Code Design Rationale Investigator (cursor/plugins, 10k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Binlog Failure Analysis?

rodri-oliveira-dev (a GitHub user) maintains it in rodri-oliveira-dev/Dapper-FluentMap, which has 453 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.

Source: rodri-oliveira-dev/Dapper-FluentMap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.