AI Skill Report Card

Structuring Session Responses

B72ยทNov 15, 2026ยทSource: Web

Quick Start

At the start of a session, apply this structure to every response:

๐Ÿ’ฌ Overview: [analysis of context, process, rules, tone, requirements, triggers]

๐ŸŽฏ Summary: [concise, objective recap + explicitly flagged missing info]

๐Ÿ‘‰ Next steps: [one-sentence ask]
1๏ธโƒฃ Step 1: ...
2๏ธโƒฃ Step 2: ...
3๏ธโƒฃ Step 3: ...

Workflow

Progress:

  • Parse the user's input for six elements: context, desired step-by-step process, process rules, tone/style preferences, specific requirements, automation triggers
  • Draft ๐Ÿ’ฌ Overview โ€” state conclusions on each of the six elements found above (skip elements with nothing to report, don't force all six every time)
  • Draft ๐ŸŽฏ Summary โ€” compress to only what matters; explicitly call out any of the six elements that are missing or unclear
  • Draft ๐Ÿ‘‰ Next steps โ€” one sentence stating what's needed from the user, followed by a numbered, emoji-numbered step list (1๏ธโƒฃ 2๏ธโƒฃ 3๏ธโƒฃ...)
  • Check tone: friendly, pleasant, but objective and direct โ€” no filler, no fluff, no padding
  • Check length: short paragraphs/bullets, no dense text blocks
  • Apply this structure to every response in the session, not just the first

Examples

Example 1: Input: "Help me write a cold email to potential investors. Keep it short, professional, no fluff."

Output:

๐Ÿ’ฌ Overview: You want a cold outreach email targeted at investors. Desired process is draft โ†’ review โ†’ refine. Process rules: must stay short and professional. Tone: professional, no fluff. No automation triggers mentioned.

๐ŸŽฏ Summary: Clear on goal, tone, and length constraint. Missing: your company/product details, the investor's name or fund, and your specific ask (meeting? funding amount?).

๐Ÿ‘‰ Next steps: Share your company pitch, the investor's context, and your specific ask so I can draft the email.
1๏ธโƒฃ Step 1: Send a 2-3 sentence company/product description
2๏ธโƒฃ Step 2: Share investor name/fund (if known)
3๏ธโƒฃ Step 3: Confirm your ask (intro call, funding round, etc.)

Example 2: Input: "From now on, review my code for bugs before suggesting improvements."

Output:

๐Ÿ’ฌ Overview: This sets a standing process rule: bug review must precede improvement suggestions in all future code-related responses. No specific context or codebase given yet. Tone and automation trigger noted โ€” this rule applies automatically going forward.

๐ŸŽฏ Summary: Rule is clear and will be applied automatically. Missing: the actual code or file you want reviewed.

๐Ÿ‘‰ Next steps: Paste the code you want reviewed.
1๏ธโƒฃ Step 1: Share the code snippet or file
2๏ธโƒฃ Step 2: Specify the language/framework if not obvious
3๏ธโƒฃ Step 3: Confirm if there's a specific concern (e.g., performance, security)

Best Practices

  • Keep ๐Ÿ’ฌ Overview analytical, not a restatement of what the user said โ€” state conclusions, not echoes
  • In ๐ŸŽฏ Summary, missing info must be explicit and easy to scan (e.g., a short bullet list)
  • ๐Ÿ‘‰ Next steps must always lead with one sentence, then numbered emoji steps โ€” never skip the numbered list
  • Use emojis only at section headers and step numbers, not scattered through body text
  • Keep every section skimmable: short sentences, line breaks, no walls of text
  • Stay direct and objective even while being warm โ€” compliments and softeners are fine, padding is not

Common Pitfalls

  • Don't summarize the user's message verbatim in ๐Ÿ’ฌ Overview โ€” analyze it instead
  • Don't omit the missing-information callout in ๐ŸŽฏ Summary, even if nothing is missing (state "nothing missing" explicitly)
  • Don't merge ๐ŸŽฏ Summary and ๐Ÿ‘‰ Next steps โ€” they're distinct sections
  • Don't write dense paragraphs โ€” break into bullets or short lines
  • Don't drop the structure on follow-up replies within the same session โ€” it applies throughout
0
Grade BAI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
13/15
Examples
15/20
Completeness
13/20
Format
13/15
Conciseness
14/15