base44-troubleshooter

Troubleshoot production issues using backend function logs. Use when investigating app errors, debugging function calls, or diagnosing production problems in Base44 apps.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, executable troubleshooting guide with a clear sequenced flow, an explicit auth validation checkpoint, and a well-signaled one-level reference for command detail. It assumes Claude's competence and earns its tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean commands and brief instructions with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor 3.	3 / 3
Actionability	Executable commands like "npx base44 logs --level error" and "npx base44 whoami" are copy-paste ready with appropriately parameterized placeholders, matching anchor 3.	3 / 3
Workflow Clarity	A front-loaded prerequisite validation ("Verify authentication before fetching logs") with a remediation feedback loop plus a clearly numbered 1-4 diagnostic sequence matches anchor 3; operations are read-only so the destructive-feedback cap does not apply.	3 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a one-level-deep reference ([project-logs.md](references/project-logs.md)) which exists and holds the detailed options/syntax, matching the well-split anchor 3.	3 / 3
	Total	12 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, concise, and clearly pairs a what-statement with an explicit Use-when trigger clause scoped to a distinct Base44 niche. Its only weakness is that the action verb is a single generic term rather than a list of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Quotes "Troubleshoot production issues using backend function logs" name the domain and method but offer only one generic action ("troubleshoot"), matching anchor 2 rather than the multiple concrete actions of anchor 3.	2 / 3
Completeness	It states both what ("Troubleshoot production issues using backend function logs") and when via an explicit "Use when..." clause, satisfying anchor 3.	3 / 3
Trigger Term Quality	Quotes "investigating app errors, debugging function calls, or diagnosing production problems" give several natural phrases a user would say, matching the good coverage of anchor 3.	3 / 3
Distinctiveness Conflict Risk	The niche "Base44 apps" with production-log triggers is clearly scoped and unlikely to fire for unrelated skills, matching anchor 3.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/base44/skills/base44-troubleshooter/SKILL.md
Commit: 11c74d6

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.