base44-sdk

The base44 SDK is the library to communicate with base44 services. In projects, you use it to communicate with remote resources (entities, backend functions, ai agents) and to write backend functions. This skill is the place for learning about available modules and types. When you plan or implement a feature, you must learn this skill

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/base44/skills/base44-sdk/SKILL.md

Quality

Content

85%

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

The body is highly actionable with executable examples and a clean overview-to-reference structure, and its entry workflow is an unambiguous branching checklist. Its main weakness is redundancy in the skill-selection framing sections, which inflates the token budget.

Suggestions

Collapse the "Immediate Action Required", "State Check Logic", and "Skill Dependencies" sections into a single concise decision table to remove redundancy.

Move the large wrong-vs-correct hallucination tables into QUICK_REFERENCE.md and keep only a one-line pointer plus the most common pitfalls inline.

Trim instructional framing phrases like "DO NOT read documentation files or search the web before acting" that pad tokens without adding SDK knowledge.

Dimension	Reasoning	Score
Conciseness	Most content is base44-specific knowledge Claude lacks (method names, wrong/correct tables), but the "Immediate Action Required", "State Check Logic", and "Skill Dependencies" sections are redundant with each other and verbose, so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code (CRUD, createClient, backend Deno.serve), specific method names, and concrete wrong-vs-correct tables that give exact guidance.	3 / 3
Workflow Clarity	The entry-point decision flow is a clear sequenced checklist (check base44/config.jsonc -> branch to implement vs. transfer to base44-cli) with explicit branches; the operations involved are not destructive/batch, so no validation loop is required.	3 / 3
Progressive Disclosure	The body is an overview with well-signaled, one-level-deep references (SDK Modules table and inline links to references/entities.md, auth.md, QUICK_REFERENCE.md, client.md, etc.), all of which exist, with details appropriately split into reference files.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 answers both what and when with an explicit trigger, but its actions are described with vague verbs and its trigger terms are not distinctive enough to avoid overlap with base44-cli. Tightening the verbs and adding more natural, specific trigger phrases would raise it.

Suggestions

Replace vague verbs ("communicate with", "learn about") with specific concrete actions (e.g., "create, list, update, and delete entities; invoke backend functions; chat with AI agents").

Add a "Use when..." clause with natural user phrasing (e.g., "Use when writing Base44 SDK code in an existing Base44 project") and broaden trigger terms.

Distinguish from base44-cli explicitly in the description (e.g., note this skill is for feature work in an already-initialized project, not project creation).

Dimension	Reasoning	Score
Specificity	Names the base44 domain and concrete resource types ("entities, backend functions, ai agents") plus the action "write backend functions", but the governing verbs are vague ("communicate with", "learn about") rather than a comprehensive list of specific actions.	2 / 3
Completeness	Clearly states what it does ("library to communicate with base44 services... communicate with remote resources... write backend functions") and provides an explicit when clause ("When you plan or implement a feature, you must learn this skill").	3 / 3
Trigger Term Quality	Includes relevant keywords a base44 user would say ("base44 SDK", "entities", "backend functions", "ai agents") and a trigger ("plan or implement a feature"), but lacks common natural variations and the trigger reads more as an instruction than natural user phrasing.	2 / 3
Distinctiveness Conflict Risk	The base44 niche is distinct, but the trigger "plan or implement a feature" is generic and risks overlap with the companion base44-cli skill and general coding skills; nothing in the description distinguishes it from base44-cli.	2 / 3
	Total	9 / 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-sdk/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.