debug-session — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited debug-session (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use Shipbook MCP tools to debug what happened in a specific user's session.
get-account-apps to identify the app (returns name, appId, platform, key, integration). If the user didn't specify an app, detect the current project's platform and filter matching apps. If there are still multiple matches, ask the user which one.get-logs filtered by the user identifier provided (email, userId, userName, udid) with severity=Error to find problems.session ID from the error log and call get-logs again with maxOrderId set to the error's orderId + 10 and without severity filter — this shows the context leading up to the error.fileName and lineNumber — use these to locate and read the actual code in the project to understand what happened.minOrderId/maxOrderId to navigate through long sessions.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.