Skip to content
Back to skills

Project Platform Diagnose

ASecurity

Overlay for environment-sensitive diagnosis — service startup, install issues, platform integration, headless/container behavior, and runtime smoke checks. Portable across repos where build, install, or runtime behavior depends on the local platform.

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 28, 2026
ai-agentsdebugging

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add n-n-code/n-n-code-skills --skill project-platform-diagnose --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Project Platform Diagnose?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Project Platform Diagnose
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/n-n-code-project-platform-diagnose/badge)](https://www.skillsdirectory.com/skills/n-n-code-project-platform-diagnose)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: project-platform-diagnose
description: Overlay for environment-sensitive diagnosis — service startup, install issues, platform integration, headless/container behavior, and runtime smoke checks. Portable across repos where build, install, or runtime behavior depends on the local platform.
---

# Project Platform Diagnose

This is a diagnostic overlay, not a standalone workflow.
Use alongside the repo's implementation skill when debugging environment-sensitive
issues.

## When to use

The problem involves build/install failures, runtime environment issues, platform
integration, or headless/container behavior.

## Not for

Logic bugs in repo-owned code (use the implementation skill directly), vendored
dependency issues (use **project-vendor-boundary**), or config behavior (use
**project-config-and-tests**).

## Rules

- separate build/install failures from runtime failures
- separate environment limits from app regressions
- prefer built-in diagnostics and reproducible smoke checks before guessing
- treat headless/container failures carefully when the feature expects a richer
  desktop or service environment

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…