Source profileQuality 75/100Review permissions

sonichi/sutando/skills/self-diagnose/SKILL.md

self-diagnose

Sutando introspection — read logs + git + memory + build log for a chosen time window and produce a concise narrative of what the agent has been doing, what's broken, and what to prioritize next.

Source repository stars
359
Declared platforms
0
Static risk flags
2
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Read Sutando's own observable state (logs, git, memory, build log, pending questions, health check, cold-review log) over a chosen window and produce a structured narrative:

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/sonichi/sutando --skill "skills/self-diagnose"
    Safe inspection promptEditorial

    Inspect the Agent Skill "self-diagnose" from https://github.com/sonichi/sutando/blob/6a8f0fccd32e5aa620a3572c8885544f144bb6fe/skills/self-diagnose/SKILL.md at commit 6a8f0fccd32e5aa620a3572c8885544f144bb6fe. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Flow

      1. Gather. Run bash skills/self-diagnose/scripts/gather.sh [window] — collects log tails, git log, buildlog.md tail, pending-questions, health-check output, cold-review-log, and recent Discord activity into /tmp/sutando-diagnose-/. 2. Synthesize. Read each gathered file. Group f…

      Gather. Run bash skills/self-diagnose/scripts/gather.sh [window] — collects log tails, git log, buildlog.md tail, pending-questions, health-check output, cold-review-log, and recent Discord activity into /tmp/sutando-di…Synthesize. Read each gathered file. Group findings under the three headings above. Be concrete: cite log lines, PR numbers, timestamps. Skip speculation.Save. Write the report to notes/diagnose-YYYY-MM-DD-HHMM.md with frontmatter (title, date, tags: [diagnose, self]).
    2. 02

      Cross-node mode (resolves 421)

      When Sutando works on one machine but is broken on another, the helper script runs gather.sh on both sides over SSH and produces a structured comparison:

      When Sutando works on one machine but is broken on another, the helper script runs gather.sh on both sides over SSH and produces a structured comparison:bash bash skills/self-diagnose/scripts/gather-remote.sh [window]
    3. 03

      e.g.

      bash skills/self-diagnose/scripts/gather-remote.sh mac-mini bash skills/self-diagnose/scripts/gather-remote.sh user@macbook.local 6h

      Cites specific log timestamps (18:28:16 — transport 1006 after NoteView injection) rather than "some errors happened"Lists PRs by number + status (394 mergeable no reviews, 354 retention sweep open)Separates recurring from one-off issues
    4. 04

      Default window

      24 hours if unspecified. Accept: 24h, 3d, 1w. Longer windows = broader scope, higher token cost.

      24 hours if unspecified. Accept: 24h, 3d, 1w. Longer windows = broader scope, higher token cost.

    Permission review

    Static risk signals and limitations

    Reads files

    low · line 16

    The documentation asks the agent to read local files, directories, or repositories.

    **Synthesize.** Read each gathered file. Group findings under the three headings above. Be concrete: cite log lines, PR numbers, timestamps. Skip speculation.

    Runs scripts

    medium · line 26

    The documentation asks the agent to run terminal commands or scripts.

    bash skills/self-diagnose/scripts/gather-remote.sh <ssh-target> [window]

    Runs scripts

    medium · line 28

    The documentation asks the agent to run terminal commands or scripts.

    bash skills/self-diagnose/scripts/gather-remote.sh mac-mini

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score75/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars359SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    sonichi/sutando
    Skill path
    skills/self-diagnose/SKILL.md
    Commit
    6a8f0fccd32e5aa620a3572c8885544f144bb6fe
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Self-Diagnose

    Read Sutando's own observable state (logs, git, memory, build log, pending questions, health check, cold-review log) over a chosen window and produce a structured narrative:

    • What's been happening — significant events, PRs shipped, tasks processed, user interactions
    • What's broken — errors in logs, pending questions, health-check failures, 1006/1011/1007 transport events, unresolved bugs surfaced in logs
    • What I'd do next — concrete prioritized actions grounded in what was observed

    Usage: /self-diagnose [--since 24h]

    ARGUMENTS: $ARGUMENTS

    Flow

    1. Gather. Run bash skills/self-diagnose/scripts/gather.sh [window] — collects log tails, git log, build_log.md tail, pending-questions, health-check output, cold-review-log, and recent Discord activity into /tmp/sutando-diagnose-<ts>/.
    2. Synthesize. Read each gathered file. Group findings under the three headings above. Be concrete: cite log lines, PR numbers, timestamps. Skip speculation.
    3. Save. Write the report to notes/diagnose-YYYY-MM-DD-HHMM.md with frontmatter (title, date, tags: [diagnose, self]).
    4. Summarize. Reply to the caller with a 5–10 line executive summary + path to the full report.

    Cross-node mode (resolves #421)

    When Sutando works on one machine but is broken on another, the helper script runs gather.sh on both sides over SSH and produces a structured comparison:

    bash skills/self-diagnose/scripts/gather-remote.sh <ssh-target> [window]
# e.g.
bash skills/self-diagnose/scripts/gather-remote.sh mac-mini
bash skills/self-diagnose/scripts/gather-remote.sh user@macbook.local 6h

    Output: /tmp/sutando-diagnose-cross-<ts>/{local,remote,diff.md} plus a persisted copy at notes/diagnose-cross-node-<YYYY-MM-DD>.md. The comparison report surfaces commit drift, health-check differences, voice-agent error counts, quota state, and PR-view divergence per side.

    Override the remote sutando path via SUTANDO_REMOTE_REPO=/path/on/peer if the failing node's checkout isn't at the default ~/Desktop/sutando.

    Security posture (per #421): read-only on the remote (only gather.sh runs there, no mutation), allowlist enforced by gather.sh's existing scope (no .env, no tokens), per-session SSH (no daemon, no persistent state on the remote).

    Default window

    24 hours if unspecified. Accept: 24h, 3d, 1w. Longer windows = broader scope, higher token cost.

    What a good report looks like

    • Cites specific log timestamps (18:28:16 — transport 1006 after NoteView injection) rather than "some errors happened"
    • Lists PRs by number + status (#394 mergeable no reviews, #354 retention sweep open)
    • Separates recurring from one-off issues
    • Prioritizes "what I'd do next" by impact and blocking, not by what's most recent

    What to skip

    • Verbose log dumps — the gathered files are on disk already; just reference them
    • Speculation without log evidence — "maybe the Gemini server is..." should be backed by a log line showing the close code and preceding event
    • Restating CLAUDE.md / build_log.md content — those are already durable; only surface what's NEW in the window

    Related

    • notes/cold-review-capability.md — sister capability for PR-level review
    • notes/voice-transport-1006-hypothesis.md — example of the depth of analysis a self-diagnose report should match
    • build_log.md — the canonical "what has been built" log; complements but doesn't replace

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    2026-07-270 platforms
    Computed 10042,015

    coreyhaines31/marketingskills

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

    2026-07-270 platforms
    Computed 997

    event4u-app/agent-config

    design-review

    Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

    2026-07-280 platforms
    Computed 9831,966

    K-Dense-AI/scientific-agent-skills

    dask

    Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

    2026-07-280 platforms