AI Skill Report Card

Delivering Complete Projects

B70·Nov 19, 2026·Source: Web
13 / 15

When given a project description, immediately:

  1. Restate the project goal in one line to confirm understanding.
  2. List all components needed (frontend, backend, database, config, deployment).
  3. Deliver all files together — no placeholders like "add your logic here" unless explicitly requested.
  4. End with a short "Suggestions" section: performance, security, scalability improvements.

No long preamble. No asking unnecessary clarifying questions if the request is clear enough to proceed with reasonable defaults — state assumptions instead of asking.

Recommendation▾
Examples show only described outputs, not actual concrete code/file contents — include at least one fully rendered short example (e.g., actual server.js snippet) to demonstrate the 'no placeholders' standard in practice.
12 / 15

Progress:

  • Parse the request fully (including any non-English/mixed-language input) before responding
  • Identify the full scope: every file/module the project needs to actually run
  • Choose sensible defaults for unspecified details (stack, folder structure, naming) and state them briefly
  • Write all code so components are wired together (imports, routes, configs match across files)
  • Verify nothing references a function/file/env var that wasn't actually created
  • Add a short "How to run" block (install, env vars, start command)
  • Add a "Suggestions" block: 2-5 concrete improvements (performance, security, architecture)
  • Keep prose minimal — let code and structured lists carry the explanation
Recommendation▾
Add a bad-output example (e.g., a snippet with '// add logic here') contrasted with the good output, since the skill explicitly forbids this pattern.
11 / 20

Example 1: Input: "اعملي API بسيط بـ Node.js فيه تسجيل دخول و قاعدة بيانات" Output: Full project — server.js, routes/auth.js, models/User.js, config/db.js, .env.example, package.json with correct dependencies, JWT auth wired end-to-end, plus a "Suggestions" section covering rate-limiting, password hashing check (bcrypt), and adding refresh tokens.

Example 2: Input: "ضيف ميزة رفع صور للمشروع يلي قبل" Output: New routes/upload.js + middleware/multer.js, updated server.js to mount the route, updated package.json dependencies, and a note confirming it integrates with existing auth middleware — not a standalone disconnected snippet.

Recommendation▾
Workflow checklist is solid but could include a concrete file-dependency verification step or example of catching a broken import, since that's a named pitfall.
  • Always deliver interconnected files as one coherent unit — treat the chat response like a repo, not isolated snippets.
  • State assumptions explicitly ("Assuming Node.js + Express + MongoDB") instead of stalling with questions.
  • Default to current, stable, widely-used libraries unless the user specifies otherwise.
  • Keep explanations compact: bullet points > paragraphs.
  • Match the user's language (Arabic/English/mixed) in explanations, but keep code and identifiers in English.
  • Always include error handling and env-based config — never hardcode secrets.
  • When modifying an existing project, show exactly which files changed and how they connect to what already exists.
  • Don't deliver partial code with "// rest of implementation here" — finish it.
  • Don't introduce a function/import that isn't defined elsewhere in the delivered files.
  • Don't over-explain basic concepts (what REST is, what npm is) — assume competence.
  • Don't ask multiple clarifying questions when a reasonable default exists — pick one and state it.
  • Don't silently ignore part of a multi-part request — address every requirement mentioned.
  • Don't forget the "suggestions" section — it's a required differentiator, not optional.
0
Grade BAI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
13/15
Workflow
12/15
Examples
11/20
Completeness
13/20
Format
14/15
Conciseness
13/15