From a0e9684270374341571e7cfde30c7d3216d34bd3 Mon Sep 17 00:00:00 2001 From: Connor Rhodes Date: Thu, 2 Apr 2026 21:17:38 -0500 Subject: [PATCH] Add pro-dev-justification skill, build log; remove meeting-notes skill Co-Authored-By: Claude Sonnet 4.6 --- _build-log.md | 25 ++++++++++++++++ meeting-notes/SKILL.md | 54 ---------------------------------- pro-dev-justification/SKILL.md | 45 ++++++++++++++++++++++++++++ 3 files changed, 70 insertions(+), 54 deletions(-) create mode 100644 _build-log.md delete mode 100644 meeting-notes/SKILL.md create mode 100644 pro-dev-justification/SKILL.md diff --git a/_build-log.md b/_build-log.md new file mode 100644 index 0000000..affce5b --- /dev/null +++ b/_build-log.md @@ -0,0 +1,25 @@ +# Robot Assistant Field Guide Build Log + +## Video 3 — CLAUDE.md +**Date:** 2026-02-23 +**Name:** Connor +**Role:** Solutions engineer at a physical security company +**Key preferences:** +- Address by first name +- Keep responses concise unless detail is asked for +- Casual and direct with Connor; polite and consultative with outside parties +- Never use the word "delve" +- Always ask before making changes to existing files +- Never use em-dashes in writing; use commas or colons instead +**Files created:** CLAUDE.md (now AGENTS.md) + +--- + +## Video 4 — First Skill +**Date:** 2026-04-02 +**Skill:** pro-dev-justification +**Purpose:** Writes a single-paragraph business justification for professional development expenses; audience is Connor's manager and HR +**Triggers:** "pro dev expense", "professional development expense", "write a business case for a pro dev expense", "write a justification for a pro dev expense", "professional development business case" +**Files created:** skills/pro-dev-justification/SKILL.md + +--- diff --git a/meeting-notes/SKILL.md b/meeting-notes/SKILL.md deleted file mode 100644 index 9756ffe..0000000 --- a/meeting-notes/SKILL.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: meeting-notes -description: Summarize raw meeting notes into a clean, formatted summary with decisions, action items, and follow-ups. -triggers: - - summarize meeting - - meeting notes - - what happened in the meeting - - meeting summary ---- - -# Meeting Notes - -Take raw, unstructured meeting notes and produce a clean summary. - -## When to Use - -Use this skill when someone provides rough notes, a transcript, or bullet points from a meeting and wants them organized into a readable summary. - -## Instructions - -1. Read the raw notes provided. -2. Identify: meeting title (or infer from content), date (if mentioned), and attendees (if mentioned). -3. Produce a formatted summary with these sections: - -### Output Format - -**Meeting:** [Title] -**Date:** [Date if known] -**Attendees:** [Names if known] - -**Summary** -[2–4 sentence overview of what the meeting covered] - -**Key Decisions** -[Bullet list of decisions made — who decided what] - -**Action Items** -[Bullet list — each item includes: what needs to be done, who owns it, and any deadline mentioned] - -**Follow-Up Items** -[Anything that needs future attention but isn't an immediate action] - -## Rules - -- Keep the summary under 300 words unless the meeting was unusually long. -- Use bullet points for decisions, action items, and follow-ups. -- Bold the names of people assigned to action items. -- Use professional but clear language. Active voice. -- If information is missing (no date, no attendees), skip that field rather than guessing. -- Never invent details that weren't in the original notes. - ---- - -*Started with the Robot Assistant Field Guide Starter Kit. Customized in Video 4 via the assembler.* diff --git a/pro-dev-justification/SKILL.md b/pro-dev-justification/SKILL.md new file mode 100644 index 0000000..684606a --- /dev/null +++ b/pro-dev-justification/SKILL.md @@ -0,0 +1,45 @@ +--- +name: pro-dev-justification +description: Write a business justification for a professional development expense. Produces a single, factual paragraph for a manager and HR audience. +triggers: + - pro dev expense + - professional development expense + - write a business case for a pro dev expense + - write a justification for a pro dev expense + - professional development business case +--- + +# Pro Dev Justification + +Write a concise business justification for a professional development purchase. + +## When to Use + +When Connor needs to justify a training, tool, book, course, or other professional development expense to his manager and HR. + +## Instructions + +1. Ask for the following if not provided: + - Resource name or description + - Specific technical topics it covers + +2. Write a single, direct paragraph using the template below. + +3. Do not ask follow-up questions or offer alternatives — just produce the paragraph. + +## Rules + +- Strictly factual: only state what the resource actually contains and what it will be used for +- No hyperbole or marketing language: avoid words like "comprehensive," "revolutionary," "invaluable," "highly cost-effective" +- Single paragraph, no headers, no bullet points +- Keep benefits general — audience is manager and HR, not a technical reviewer +- Focus on practical application: reference material, instructions, and documentation for designing, building, and testing proofs of concept +- Context: Connor is a Solutions Engineer at a physical security company working on hardware-software integration, edge computing, IoT development, and DC electronics + +## Output Template + +"Purchasing `[Resource Name]` provides reference material for `[specific technical topics]`. The [resource type] contains specific instructions and documentation for designing, building, and testing electrical proof of concepts. Acquiring this resource supports my professional development by expanding my technical capabilities, enabling me to execute the hardware prototyping required for our engineering initiatives." + +## Example Output + +> Purchasing this bundle of technical books on ESP32, Raspberry Pi, and Arduino provides reference material for hardware-software integration, edge computing, and IoT development. The texts contain specific instructions and documentation for designing, building, and testing electrical proof of concepts. Acquiring these resources supports my professional development by expanding my technical capabilities, enabling me to execute the hardware prototyping required for our engineering initiatives.