Borrowing it
Nothing to install: this file belongs to ingen084/KyoshinEewViewerIngen. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ingen084/KyoshinEewViewerIngen/develop/.claude/skills/kevi-build-troubleshoot/SKILL.mdgit clone --depth 1 https://github.com/ingen084/KyoshinEewViewerIngenWrote 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.
[](https://agentmods.dev/skills/ingen084/kyoshineewvieweringen/kevi-build-troubleshoot)<a href="https://agentmods.dev/skills/ingen084/kyoshineewvieweringen/kevi-build-troubleshoot"><img src="https://agentmods.dev/badge/skills/ingen084/kyoshineewvieweringen/kevi-build-troubleshoot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ingen084/kyoshineewvieweringen/kevi-build-troubleshoot"><img src="https://agentmods.dev/badge/skills/ingen084/kyoshineewvieweringen/kevi-build-troubleshoot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00095 | $0.01234 |
| Opus 5 | $0.00048 | $0.00617 |
| Sonnet 5 | $0.00019 | $0.00247 |
| Haiku 4.5 | $0.00010 | $0.00123 |
Grade A, and why
kevi-build-troubleshoot 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 12d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KEViのビルド・テストのトラブルシューティング
Instructions
git管理外ディレクトリ (CSVソースジェネレータ)
KyoshinEewViewer.csproj のCSVソースジェネレータは、リポジトリ直下の git管理外 ディレクトリ jma-code-dictionary/csv/ に依存する。
git worktreeでビルドする場合、このディレクトリは自動では付いてこないため、本体リポジトリのものをJunctionでリンクする必要がある:
New-Item -ItemType Junction -Path <worktree>\jma-code-dictionary -Target <本体repo>\jma-code-dictionary
これを忘れるとソースジェネレータがCSVを見つけられずビルドが失敗する。
DesktopプロジェクトのTFMはホストOSで切り替わる
common.props は全プロジェクト net10.0 単一だが、KyoshinEewViewer.Desktop だけは自csproj内の Condition="$([MSBuild]::IsOSPlatform('Windows'))" で Windowsホストのときだけ net10.0-windows10.0.19041.0 に上書きされる。
これは意図的な設計で、狙いは「非Windows開発機で -f 指定なしの dotnet run/F5を可能にしつつ、Windowsでも無駄なnet10.0ビルドとマルチTFM特有の #if WINDOWS 並び順ハックを排除する」こと。Desktopは他のどのcsprojからも参照されない葉プロジェクトなので、net10.0出力を必要とする消費者が存在せず、この非対称な上書きが成立する。
これによる既知の挙動:
- Windows機で
dotnet build -f net10.0はNETSDK1005で失敗する。net10.0変種はWindowsホストではrestoreされないためで、バグではない。Windowsではフレームワーク指定なしでビルドする（windows TFMになる）。 -p:TargetFramework=net10.0のグローバルプロパティ指定も不可（restoreがTargetFrameworkグローバルプロパティを無視してwindows TFMをrestoreするため同じくNETSDK1005になる。-p:TargetFrameworks併用は推移プロジェクトの評価を壊しMSB4022になる）。- Windows機で
#if !WINDOWSコード（Linux/macOS通知プロバイダ・DBusトレイ検出等）をコンパイル検証したい場合は、csprojのTFM上書き条件を一時的にCondition="false"に書き換えてdotnet build（common.propsのnet10.0が有効になりrestoreも通る）。検証後は条件を戻し、bin\Debug\net10.0を消して再ビルドすれば元の状態に戻る。この書き換えはコミットしないこと。 - CI（release.yml）は各OSランナー上で
-fを明示している（windows→windows TFM、ubuntu/mac→net10.0）ので成立する。ローカルとCIでTFMが違って見えても正常。 - 過去にあった
KeviMultiTargetopt-in・多TFM方式は廃止済み。ビルドエラー対処としてマルチTFM化へ「戻す」修正をしないこと。
既知の失敗するテスト（電文系）
tests/KyoshinEewViewer.Tests の電文系（Dmdata/TelegramProvideService系）テスト約50件は、変更前のHEADでも失敗する既存問題（2026-06-13、HEAD worktreeで確認済み）。タイミング依存の並行テストで、フルセット実行には8分超かかる。
これらの失敗は自分の変更のせいではないことが多いので、震源推定など無関係な変更を検証する際は、フィルタで関係分のみ実行するとよい:
dotnet test --filter "FullyQualifiedName~Epicenter|FullyQualifiedName~Templates"
これなら数十msで完了する。
使い分けの判断
テスト失敗の名前が電文系（履歴電文・サブスクライバー・Restore等）を含む場合は、まずこのスキルを参照し、フィルタ実行で自分の変更由来かどうかを判断する。50件の失敗を毎回8分×2（変更前後）で切り分け直すのは無駄。
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.
- 12d ago First seen · 51 lines · 95 tokens per session scan A 5731e962db9b
kevi-build-troubleshoot is a skill published in the GitHub repository ingen084/KyoshinEewViewerIngen (187 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 1,234 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
performance-optimization-dotnet
Optimizes .NET/C# application performance — measure first with BenchmarkDotNet / dotnet-counters / dotnet-trace / PerfView, then fix the specific bottleneck (EF Core N+1, sync-over-async, Gen2 GC pressure, thread-pool starvation, allocation hotspots, unbounded queries, missing pagination, Kestrel misconfiguration).…
debugging-and-error-recovery
Guides systematic root-cause debugging for .NET/C# code. Use when dotnet test fails, dotnet build breaks, behavior doesn't match expectations, or you encounter any unexpected error (NullReferenceException, TaskCanceledException, missing DI registration, EF Core migration conflict). Use when you need a systematic…
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
check-bin-obj-clash
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing/overwritten…
build-perf-diagnostics
Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization…
dump-collect
Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps…