{ "schemaVersion": "1.0", "item": { "slug": "proposal-and-coverletter-interviewer-improver", "name": "Proposal and Cover Letter Interviewer & Improver (Continuous Questions and Memory for Better Proposals/Cover Letters by Getting to Know You)", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/drafthead/proposal-and-coverletter-interviewer-improver", "canonicalUrl": "https://clawhub.ai/drafthead/proposal-and-coverletter-interviewer-improver", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/proposal-and-coverletter-interviewer-improver", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=proposal-and-coverletter-interviewer-improver", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/proposal-and-coverletter-interviewer-improver" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/proposal-and-coverletter-interviewer-improver", "agentPageUrl": "https://openagent3.xyz/skills/proposal-and-coverletter-interviewer-improver/agent", "manifestUrl": "https://openagent3.xyz/skills/proposal-and-coverletter-interviewer-improver/agent.json", "briefUrl": "https://openagent3.xyz/skills/proposal-and-coverletter-interviewer-improver/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Proposal & Cover Letter Discovery Interview", "body": "This is NOT a CV builder. This skill creates high-quality, reusable statements for proposals and cover letters by running a structured interview to extract personal-but-professional facts." }, { "title": "The Problem with Generic Letters", "body": "Generic cover letter and proposal writers are bland because they don't know YOU. They can't capture:\n\nYour living in Dubai and Seoul, and what that taught you about cross-cultural collaboration\nThe robotics project you tinkered with at home that shows your passion\nThe class that changed how you think about systems\nThe boring job that taught you what quality really means\nYour unfair advantage that clients actually hire you for\n\nThis skill solves that through interview → facts → statements → approval → assembly." }, { "title": "Phase 1: Discovery Interview", "body": "The skill asks structured questions to extract:\n\nGeographic and cultural context (places lived, travel, cross-cultural work)\nWork experience beyond the resume (lessons, standout moments, what colleagues rely on you for)\nEducation (specific classes, formative learning, projects)\nProjects and proof (side projects, demos, artifacts)\nAwards and recognition (scholarships, competitions, certifications)\nPast hobbies (skills hidden in former interests)\nBooks and influences (working philosophy)\nThe boring stuff (what you learned from frustrating work)\nProposal leverage (what you want to be hired for)\nConstraints (topics to avoid, boundaries)" }, { "title": "Phase 2: Statement Generation", "body": "From gathered facts, the skill drafts 3-8 candidate statements per round. Each statement:\n\nIs grounded in real facts (no invention)\nIs usable in proposals/cover letters\nHas multiple variants (Upwork short, standard cover letter, technical/proof-first)\nHas tags (#leadership #robotics #global-living)" }, { "title": "Phase 3: Approval Loop", "body": "You review each statement: Approve / Edit / Reject\n\nApproved statements go into statements.md\nEdits refine the statement and update preferences\nRejections inform future drafting" }, { "title": "Phase 4: Assembly (Future)", "body": "When you need a proposal, the skill pulls relevant approved statements and assembles them for the target platform and company." }, { "title": "Storage Model: Folders + Files", "body": "All data is stored INSIDE the skill folder at:\nskills/proposal-interview/personal/ and skills/proposal-interview/companies/" }, { "title": "Directory Structure", "body": "skills/proposal-interview/\n personal/\n /\n profile.md # Current snapshot: name, what they do, where, objectives (ALWAYS READ FIRST)\n user.md # Raw facts about this person (APPEND ONLY - NEVER DELETE)\n statements.md # Approved statements (APPEND ONLY - NEVER DELETE APPROVED STATEMENTS)\n preferences.md # Writing style preferences\n coherence.md # Conflicts, gaps, clarifications needed\n\n companies/\n /\n profile.md # Current snapshot: company name, what they do, where, objectives\n org.md # Company facts, domain, relationships (APPEND ONLY - NEVER DELETE)\n statements.md # Company-specific approved statements (APPEND ONLY - NEVER DELETE)\n preferences.md # Company-specific style preferences\n projects.md # (Optional) Project history with this org\n coherence.md # (Optional) Company-specific conflicts/gaps" }, { "title": "Routing Rules", "body": "Personal vs Company:\n\nPersonal facts → skills/proposal-interview/personal//user.md\nCompany-specific facts → skills/proposal-interview/companies//org.md\n\nMulti-person support:\n\nDefault: current user\nIf doing this for someone else (e.g., spouse), use skills/proposal-interview/personal//\n\nRelationships:\n\nIf a company has an owner/founder relevant to letters, record in org.md" }, { "title": "File Rules (Append-Only)", "body": "⚠️ CRITICAL FOR ALL MODELS - READ THIS:\n\nNEVER DELETE OR REWRITE LINES IN ANY FILE.\nALWAYS APPEND. NEVER DELETE. ONLY ADD.\n\nThis applies to:\n\n❌ NEVER delete approved statements from statements.md\n❌ NEVER delete facts from user.md or org.md\n❌ NEVER rewrite existing lines\n✅ ALWAYS append new information\n✅ ALWAYS read existing files before appending\n\nIf a conflict is detected:\n\nAppend the new info (don't delete the old info)\nAppend a note to coherence.md\nAsk a clarifying question next round\n\nprofile.md is the EXCEPTION - this file CAN be edited/rewritten as it's a current snapshot, not a permanent record.\n\nprofile.md (personal or company) — ALWAYS READ FIRST\n\nCurrent snapshot of the person or company. Simple, clear, updated format.\n\nPersonal profile.md format:\n\n# [Full Name]\n\n## What They Do\n[Simple description - \"AI consultant specializing in OpenClaw implementations and AI strategy\"]\n\n## Where Based\n[Location - \"Amsterdam, Netherlands\" or \"Remote\" or \"San Francisco, CA\"]\n\n## Primary Objective\n[Main goal for proposals/applications - \"Secure OpenClaw implementation contracts with mid-size tech companies\"]\n\n## Secondary Objective (Optional)\n[Secondary goal - \"Build reputation as AI strategy consultant for startups\"]\n\n## Current Status\n[Brief context - \"Actively applying to Upwork projects and direct outreach to companies\"]\n\n## Last Updated\n[Date - \"2026-02-24\"]\n\nCompany profile.md format:\n\n# [Company Name]\n\n## What They Do\n[Simple description - \"Industrial automation, warehouse robotics\"]\n\n## Where Based\n[Location - \"San Francisco, CA\"]\n\n## Primary Relationship Objective\n[Why we're tracking them - \"Potential client for OpenClaw implementation\"]\n\n## Secondary Objective (Optional)\n[Additional context - \"Investor prospect for Way Back Project\"]\n\n## Key Contact\n[Name and role if known - \"Jane Doe, CTO\"]\n\n## Last Updated\n[Date - \"2026-02-24\"]\n\nWorkflow: Always read profile.md FIRST (before user.md, statements.md, etc.) to get current context.\n\nuser.md (personal) — ⚠️ APPEND ONLY, NEVER DELETE ⚠️\n\nCRITICAL REMINDER: Before writing to this file, ALWAYS read existing content first to avoid duplicates and incorporate existing facts.\n\nRaw facts and concise notes. Facts only, no polished marketing.\n\nExample:\n\n- Lived in Dubai 2018-2020, worked with clients across EMEA\n- Lived in South Korea 2015-2017, learned Korean to intermediate level\n- Built robotic arms at home using Arduino and 3D-printed parts\n- Took MIT OCW Machine Learning course, applied to personal project predicting stock trends\n- Won regional robotics competition in high school, team captain\n- Former competitive swimmer (stopped 2016), coached youth swim team 2017-2018\n- Speaks English (native), Korean (intermediate), Arabic (basic)\n- Prefers remote work, available 9am-5pm EST\n\nstatements.md (personal or company) — ⚠️ APPEND ONLY, NEVER DELETE APPROVED STATEMENTS ⚠️\n\nCRITICAL REMINDER: Once a statement is approved and written here, NEVER delete it. Only append new approved statements. Read existing statements before generating new ones to avoid duplicates.\n\nUser-approved statements only. Each entry includes:\n\nStatement text\nTags\nEvidence pointer (which facts support this)\n\nExample:\n\n---\nstatement: \"I bring a global perspective from living and working across three continents—from collaborating with EMEA clients in Dubai to navigating cross-cultural teams in South Korea. I've learned to adapt communication styles and build trust across cultures, which is essential for remote, distributed work.\"\ntags: #global-living #dubai #korea #cross-cultural #remote-work #client-facing\nevidence: user.md lines 1-2, 7\nplatform: standard cover letter\n---\n\nstatement: \"I'm passionate about robotics and hands-on engineering—I've built robotic arms at home using Arduino and 3D-printed custom parts. This isn't just work for me; it's how I spend my evenings.\"\ntags: #robotics #hands-on #passion #arduino #3d-printing #side-projects\nevidence: user.md line 3\nplatform: Upwork short pitch, technical/proof-first\n---\n\nstatement: \"My background in competitive swimming taught me discipline and coaching—skills I later applied when coaching a youth swim team. I understand how to break down complex skills, provide feedback, and build confidence.\"\ntags: #coaching #leadership #discipline #teaching #past-hobbies\nevidence: user.md line 6\nplatform: standard cover letter, leadership-focused\n---\n\npreferences.md (personal or company)\n\nWriting style preferences by platform.\n\nExample:\n\n# Writing Preferences\n\n## Tone\n- Confident but not arrogant\n- Warm and approachable\n- Direct, minimal fluff\n- Technical when relevant (show don't just tell)\n\n## Platform Settings\n\n### Upwork\n- Length: 2-4 sentences + optional 2-3 bullet proof points\n- Structure: Hook → proof → call-to-action\n- Metrics-first when available\n\n### LinkedIn / Email Outreach\n- Length: 3-5 sentences\n- Friendly, personal, brief\n- Lead with common ground or mutual connection\n\n### Job Portal / Formal Cover Letter\n- Length: 3-4 paragraphs\n- Structured: intro → experience/proof → why this role → close\n- Slightly more formal tone\n\n### Grants / Proposals\n- Length: longer, evidence-heavy\n- Structure: narrative with metrics and citations\n- Emphasize impact and outcomes\n\n## Avoid List\n- Buzzwords: \"synergy\", \"rockstar\", \"ninja\", \"guru\"\n- Overused phrases: \"I'm passionate about\", \"proven track record\"\n- Sensitive info: exact salary history, medical details\n\n## Structure Preferences\n- Prefer bullets for proof points\n- Use short paragraphs (3-4 sentences max)\n- Open with strongest differentiator\n- Close with clear next step\n\norg.md (company)\n\nCompany/initiative facts.\n\nExample:\n\n# Acme Robotics Inc\n\n## Domain\n- Industrial automation, warehouse robotics\n- Focus on AI-driven pick-and-place systems\n- Series B funded, 50-200 employees\n\n## Key People\n- Jane Doe, Founder/CEO (former Google engineer)\n- John Smith, CTO (robotics background)\n\n## Positioning\n- \"We make warehouses smarter\"\n- Emphasis on practical, deployable solutions (not research)\n\n## Constraints\n- Remote-first company\n- Looking for senior engineers with production experience\n\n## History with User\n- Applied via Upwork 2024-02-20\n- Initial call scheduled for 2024-02-28\n\ncoherence.md (optional but recommended)\n\nTrack conflicts, gaps, clarifications needed.\n\nExample:\n\n# Coherence Notes\n\n## Possible Conflicts\n- 2024-02-24: User said \"intermediate Korean\" but earlier mentioned \"basic conversational\". Clarify level.\n\n## Missing Info\n- Need timeframe for Dubai work (years? months?)\n- Need scope/metrics for robotics project (how many built? any demos?)\n- Need GPA or honors for MIT OCW course mention\n\n## Clarifications Needed\n- Is Arabic \"basic\" = conversational or just tourist phrases?\n- Does \"remote work preference\" mean fully remote only, or hybrid OK?" }, { "title": "⚠️ QUESTION CADENCE - VERY IMPORTANT ⚠️", "body": "First time with a person (onboarding):\n\nAsk 10 initial discovery questions in one session\nThen generate first batch of statements\n\nAll subsequent sessions (updates/refinement):\n\nAsk only 3 questions per round\nThen generate statements from those 3 answers\nThis keeps sessions manageable and can run via cron for continuous learning\n\nWhy this matters: You can schedule this skill as a cron job to periodically learn more about the person (every week, every month, etc.). The 3-question pattern keeps token usage reasonable while continuously building your statement library." }, { "title": "Starting Fresh (First Run)", "body": "Read this skill document to understand the workflow\n\n\nCreate folder structure if it doesn't exist:\nmkdir -p skills/proposal-interview/personal/ skills/proposal-interview/companies\n\n\n\nCreate profile.md with current snapshot (name, what they do, where, objectives)\n\n\nExplain the process to the user:\n\"I'm going to ask you 10 onboarding questions to build your initial profile. After this first session, future updates will only ask 3 questions at a time to keep things manageable. This can even run on a schedule to continuously learn more about you.\"\n\n\nRun onboarding questions (see below)\n\n\nAsk the 10 initial discovery questions\n\n\nDraft 3-8 statements, get approval, store approved ones\n\n\nFuture sessions: switch to 3-question rounds" }, { "title": "Continuing Work (Existing User) — ⚠️ READ BEFORE WRITING ⚠️", "body": "CRITICAL: Always read existing files BEFORE asking questions or appending facts. This prevents duplicates and helps you incorporate existing knowledge.\n\nRead existing files IN THIS ORDER:\n\nskills/proposal-interview/personal//profile.md (READ FIRST - current context)\nskills/proposal-interview/personal//user.md (facts gathered - NEVER DELETE, ONLY APPEND)\nskills/proposal-interview/personal//statements.md (approved statements - NEVER DELETE, ONLY APPEND)\nskills/proposal-interview/personal//preferences.md (style guide)\nskills/proposal-interview/personal//coherence.md (gaps/conflicts)\n\n\n\nAsk only 3 new questions (fill gaps, drill down on threads)\n\n\nAppend new facts to user.md (NEVER delete existing facts, always append)\n\n\nDraft 2-4 new statements based on new facts\n\n\nGet approval, append to statements.md (NEVER delete approved statements, always append)" }, { "title": "Working with a Company/Initiative", "body": "Create company folder: skills/proposal-interview/companies//\n\n\nAsk company-specific questions:\n\nWhat do they do? Domain?\nKey people? Relationships?\nWhy is user interested?\nWhat's the user's angle/fit?\n\n\n\nStore company facts in org.md\n\n\nDraft company-specific statements (e.g., \"why I'm a fit for Acme Robotics\")\n\n\nStore in company's statements.md" }, { "title": "Question Cadence (Hard Requirement)", "body": "First-ever run for a person:\n\nAsk exactly 10 questions before generating statements\n\nAfter first batch:\n\nAsk 3 questions per round\nGenerate statements\nGet feedback\nUpdate files\nRepeat\n\nIf user gives very short answers:\n\nComment briefly: \"That's shorter than ideal, but I can work with it.\"\nAsk a follow-up only if critical" }, { "title": "Onboarding Script (Always First)", "body": "When starting with a new person, ask these setup questions:" }, { "title": "1. Who is this for?", "body": "\"Are you creating this for yourself, or for someone else (e.g., spouse, client)?\"\n\nIf for someone else, create skills/proposal-interview/personal//" }, { "title": "2. Which platforms do you use?", "body": "\"Which platforms do you apply through? Check all that apply:\n\nUpwork / Freelance marketplaces\nLinkedIn (applications or outreach)\nEmail outreach (cold/warm)\nCompany career portals\nGrants / funding applications\nOther (specify)\"" }, { "title": "3. Style preferences per platform", "body": "For each platform they checked, ask:\n\"For [platform], what's your preferred style?\n\nTone: confident / warm / direct / humble / technical / playful / formal\nLength: short (2-4 sentences) / medium (1-2 paragraphs) / long (3-4 paragraphs)\nStructure: bullets / narrative / metrics-first / story-first\nWhat does success look like? (get a reply / win a contract / advance to interview)\"" }, { "title": "4. What do you want to be hired for?", "body": "\"What type of work do you want more of? What's your unfair advantage?\"" }, { "title": "5. Anything to avoid?", "body": "\"Any topics, buzzwords, or sensitive info we should avoid in proposals?\"\n\nAfter onboarding, write preferences to skills/proposal-interview/personal//preferences.md." }, { "title": "The 10 Initial Questions (Template)", "body": "After onboarding, ask these 10 questions (adapt based on their work/goals):" }, { "title": "1. Geographic & Cultural Context", "body": "\"Where have you lived or traveled that shaped how you work? (Dubai, Seoul, remote teams, etc.) Answer in 3 bullets or a short paragraph.\"" }, { "title": "2. Work Beyond the Resume", "body": "\"What have you learned in your work that doesn't fit neatly on a resume? What was surprisingly hard and how did you handle it?\"" }, { "title": "3. What Colleagues Rely On You For", "body": "\"What do colleagues, clients, or teammates repeatedly come to you for? What's your 'thing'?\"" }, { "title": "4. Education & Formative Learning", "body": "\"Any classes, courses, or learning experiences that changed how you think or work? (Formal or self-taught—include MOOCs, bootcamps, workshops.)\"" }, { "title": "5. Projects & Proof", "body": "\"What's a project you're proud of that shows your skills? (Side project, work project, personal tinkering, GitHub repo, portfolio piece.) Describe scope and outcome.\"" }, { "title": "6. Awards & Recognition", "body": "\"Any awards, scholarships, competitions, certifications, or public recognition? (School, work, industry, community.)\"" }, { "title": "7. Past Hobbies", "body": "\"What hobbies did you used to do a lot but don't anymore? What skills did they build? (Sports, arts, teaching, community involvement, etc.)\"" }, { "title": "8. Books & Influences (Optional)", "body": "\"Any books, ideas, or people that shaped your approach to work or leadership? (Use sparingly, only if it produces something concrete.)\"" }, { "title": "9. The Boring Story", "body": "\"Tell me about a role, class, or project you found boring or frustrating. What did you learn? What do you now avoid or demand in your work?\"" }, { "title": "10. Your Unfair Advantage", "body": "\"If you had to pitch yourself in one sentence, what's your unfair advantage? What makes you different from 100 other people with similar skills?\"\n\nAfter these 10 questions:\n\nExtract facts → append to user.md\nDraft 3-8 statements (see below)\nGet approval\nStore approved statements → statements.md\nUpdate preferences.md based on feedback" }, { "title": "The 3-Question Round (Subsequent Runs)", "body": "After the initial 10 questions, switch to asking 3 questions per round.\n\nHow to choose the next 3 questions:\n\nCheck coherence.md for gaps or conflicts that need clarification\nReview statements.md to see which categories are under-represented\nDrill down on strong threads:\n\nIf user mentioned robots → ask about tools, scope, outcomes, demos\nIf user mentioned Dubai/Korea → ask about cross-cultural teamwork, languages, client communication\nIf user mentioned a specific company → ask domain-specific questions\n\nQuestion design principles:\n\nAllow short or long replies\nUse phrasing like: \"Answer in 3 bullets or a short paragraph.\"\nIf dates/metrics uncertain: \"Approximate is fine.\"\nAlways explain why it matters (briefly): \"This helps me write more personal proposals.\"\n\nAfter each 3-question round:\n\nExtract facts → append to user.md or org.md\nDraft 2-4 new statements\nGet approval\nUpdate files" }, { "title": "When to Draft Statements", "body": "After the first 10 questions (initial run)\nAfter every 3-question round (subsequent runs)" }, { "title": "How to Draft Statements", "body": "Generate 3-8 candidate statements per round.\n\nEach statement must:\n\nBe grounded in gathered facts (no invention)\nBe usable in proposals/cover letters\nBe written in multiple variants when helpful:\n\nUpwork short pitch (1-2 lines)\nStandard cover letter (2-4 sentences)\nTechnical/proof-first variant (metrics, tools, outcomes)\n\nStatement structure:\n\n---\nstatement: \"[The actual statement text]\"\ntags: #tag1 #tag2 #tag3\nevidence: user.md line X, org.md line Y\nplatform: Upwork short / standard cover letter / technical\n---" }, { "title": "Approval Process", "body": "For each statement, ask the user:\n\n\"Here's a draft statement. Choose one:\n\nApprove - Store as-is\nEdit - Suggest changes (I'll rewrite and confirm)\nReject - Don't store, move on\"\n\nIf user chooses Edit:\n\nPropose a rewrite\nGet confirmation\nIf confirmed, store\n\nIf user chooses Approve:\n\nRead existing statements.md first to avoid duplicates\nAppend the approved statement to statements.md in the correct folder (skills/proposal-interview/personal/ or skills/proposal-interview/companies/)\nNEVER delete previously approved statements\n\nIf user chooses Reject:\n\nDon't store (obviously, since it's rejected)\nNote the rejection reason in preferences.md if it reveals a style preference\n\n⚠️ CRITICAL REMINDER: Once a statement is approved and appended to statements.md, it must NEVER be deleted. Only append new approved statements." }, { "title": "Update Preferences Based on Feedback", "body": "After each approval round, update preferences.md if you learn:\n\nTone preferences (user prefers \"confident\" over \"humble\")\nLength preferences (user always wants shorter)\nStructure preferences (user likes bullets over narrative)\nWord choice (user hates \"passionate\", prefers \"focused on\")" }, { "title": "Upwork Short Pitch (2-4 sentences + bullets)", "body": "Example:\n\nI've built robotic arms at home using Arduino and 3D-printed parts—this isn't just work for me, it's how I spend my evenings. I bring 5 years of experience with ROS, Python, and mechatronics, plus a global perspective from working with EMEA and APAC clients.\n\n• Built 3 functional robotic arms with custom inverse kinematics\n• MIT OCW Machine Learning graduate (applied to robotics path planning)\n• Available for 20-30 hrs/week, overlap with US/EU time zones" }, { "title": "Standard Cover Letter (2-4 sentences)", "body": "Example:\n\nI bring a global perspective from living and working across three continents—from collaborating with EMEA clients in Dubai to navigating cross-cultural teams in South Korea. I've learned to adapt communication styles and build trust across cultures, which is essential for remote, distributed work. My technical background in robotics and hands-on engineering complements my ability to work with diverse teams and deliver practical solutions." }, { "title": "Technical / Proof-First Variant", "body": "Example:\n\nI've designed and built three functional robotic arms using Arduino, custom inverse kinematics algorithms (Python), and 3D-printed components. I completed MIT OCW's Machine Learning course and applied it to a path-planning optimization project that reduced movement time by 18%. My GitHub portfolio includes ROS packages, simulation environments (Gazebo), and documentation that's been forked 40+ times." }, { "title": "Email Outreach (3-5 sentences, friendly)", "body": "Example:\n\nHi [Name],\n\nI noticed Acme Robotics is hiring for a Senior Robotics Engineer. I've been tinkering with robotic arms at home for years—building them from scratch using Arduino and 3D-printed parts—and I'd love to bring that hands-on passion to a team working on real-world automation challenges.\n\nI've worked with clients across Dubai and South Korea, so I'm comfortable with remote collaboration and adapting to different working styles. Would you be open to a quick call to discuss the role?\n\nBest,\n[User]" }, { "title": "Grant / Long Proposal (Evidence-heavy, structured)", "body": "Example:\n\nMy unique combination of hands-on robotics experience and cross-cultural collaboration positions me well for this initiative. Over the past four years, I have:\n\n1. **Designed and built functional robotic systems**: I independently developed three robotic arms using Arduino microcontrollers, custom inverse kinematics algorithms (Python), and 3D-printed mechanical components. These projects demonstrate my ability to work across hardware, software, and mechanical design.\n\n2. **Applied machine learning to robotics**: I completed MIT OpenCourseWare's Machine Learning curriculum and applied those techniques to optimize path planning for robotic arm movement, achieving an 18% reduction in task completion time.\n\n3. **Collaborated across cultures and time zones**: My professional experience spans Dubai (EMEA clients) and South Korea (APAC teams), where I learned to navigate language barriers, cultural differences, and asynchronous communication. I speak English natively, Korean at an intermediate level, and basic Arabic.\n\nThis background enables me to contribute both technical expertise and the adaptability required for distributed, international teams." }, { "title": "How to Decide What to Ask Next", "body": "Maintain an internal checklist of what categories are covered:\n\nGeographic / cultural context\n Work experience beyond resume\n Education / formative learning\n Projects / proof\n Awards / recognition\n Past hobbies\n Books / influences\n Boring stories / frustrations\n Proposal leverage / unfair advantage\n Constraints / boundaries\n\nPrioritize questions that:\n\nFill gaps in under-represented categories\nDrill down on strong signals (unique experiences like living abroad)\nProduce demonstrable proof (projects, metrics, artifacts)\nAlign to target work (if a company/initiative is provided)" }, { "title": "Triggered Recall Questions", "body": "If user mentions robots:\n\n\"What tools did you use? What was the scope? Any metrics or demos?\"\n\"What's sitting in your office/workshop right now? How does it map to client value?\"\n\nIf user mentions Dubai/Korea:\n\n\"Tell me about a time cross-cultural communication was challenging. How did you adapt?\"\n\"What languages do you speak? At what level?\"\n\"How did living there change your approach to remote work or global clients?\"\n\nIf user mentions a specific job/company:\n\nPrioritize questions that produce domain-aligned statements\nStore company-specific learnings in skills/proposal-interview/companies//" }, { "title": "Fact Capture Rules (Very Explicit) — ⚠️ READ THEN APPEND ⚠️", "body": "CRITICAL WORKFLOW - DO THIS EVERY TIME:\n\nBEFORE appending any facts:\n\nREAD the existing user.md or org.md file to check what's already captured\nCheck for duplicates - don't re-add facts that are already there\nIncorporate existing facts when generating statements\n\nAfter each user answer:\n\nRead existing facts first (see above)\n\n\nExtract discrete factual lines from the answer\n\n\nAppend them to the correct file (NEVER delete existing content):\n\nPersonal facts → skills/proposal-interview/personal//user.md\nCompany facts → skills/proposal-interview/companies//org.md\n\n\n\nIf a fact is uncertain, ask a one-line confirmation before writing:\n\n\"You mentioned living in Dubai—was that 2018-2020, or different years?\"\n\n\n\nNever delete or rewrite previous lines. If a conflict is detected:\n\nAppend the new info (DO NOT DELETE THE OLD INFO)\nAppend a \"possible conflict\" note to coherence.md\nAsk a targeted clarifying question next round\n\nREMINDER: APPEND ONLY. NEVER DELETE. ALWAYS READ BEFORE WRITING." }, { "title": "Session 1: Onboarding + Initial 10 Questions", "body": "[Onboarding]\nMe: \"Are you creating this for yourself, or for someone else?\"\nUser: \"For myself.\"\n\nMe: \"Which platforms do you apply through? Upwork, LinkedIn, email, job portals, grants?\"\nUser: \"Upwork and LinkedIn mostly.\"\n\nMe: \"For Upwork, what's your preferred style? Tone, length, structure?\"\nUser: \"Confident but not cocky, short (2-4 sentences + bullets), metrics-first.\"\n\n[Preferences captured → write to preferences.md]\n\n[Initial 10 Questions]\nMe: \"Question 1: Where have you lived or traveled that shaped how you work?\"\nUser: \"I lived in Dubai for 2 years (2018-2020) and Seoul for 3 years (2015-2017). Dubai taught me how to work with clients across EMEA time zones. Korea taught me patience and indirect communication styles.\"\n\n[Extract facts → append to user.md]\n- Lived in Dubai 2018-2020, worked with EMEA clients\n- Lived in Seoul 2015-2017, learned indirect communication styles\n\nMe: \"Question 2: What have you learned that doesn't fit neatly on a resume?\"\nUser: \"I learned how to handle ambiguity. Clients don't always know what they want, and I've gotten good at asking clarifying questions early.\"\n\n[Extract facts → append to user.md]\n- Skilled at handling ambiguous client requirements, asks clarifying questions early\n\n[... continue through 10 questions ...]\n\n[After 10 questions: Draft statements]\nMe: \"Based on what you've shared, here are 5 draft statements. For each, tell me: Approve / Edit / Reject.\"\n\nStatement 1 (Upwork short):\n\"I bring a global perspective from living in Dubai and Seoul, where I collaborated with EMEA and APAC clients across time zones. I'm comfortable with remote work and cross-cultural communication.\"\nTags: #global-living #dubai #korea #remote-work #cross-cultural\n\nUser: \"Approve.\"\n\n[Write to statements.md]\n\nStatement 2 (Standard cover letter):\n\"I excel at navigating ambiguous client requirements. Early in projects, I ask targeted clarifying questions to uncover what clients really need—even when they don't know themselves yet.\"\nTags: #client-facing #ambiguity #discovery #consultative\n\nUser: \"Edit—sounds too soft. Make it more confident.\"\n\nMe: \"How about: 'I thrive in ambiguous situations. When clients aren't sure what they need, I ask the right questions upfront to define clear goals and avoid costly rework later.'\"\n\nUser: \"Perfect. Approve.\"\n\n[Write revised version to statements.md, update preferences.md: prefer confident tone]\n\n[... continue through all statements ...]" }, { "title": "Session 2: 3-Question Round", "body": "[Read existing files: user.md, statements.md, preferences.md, coherence.md]\n\nMe: \"I see you mentioned robotics earlier. Let's drill down on that.\"\n\nQuestion 1: \"You said you built robotic arms at home. How many? What tools and frameworks? Any demos or GitHub repos?\"\nUser: \"I've built 3 so far. Arduino for controllers, Python for kinematics, 3D-printed the parts. I have videos on YouTube and code on GitHub—one repo has 40+ forks.\"\n\n[Extract facts → append to user.md]\n- Built 3 robotic arms at home: Arduino controllers, Python kinematics, 3D-printed parts\n- YouTube demos, GitHub repo with 40+ forks\n\nQuestion 2: \"What was the hardest part of building them?\"\nUser: \"Getting the inverse kinematics right. Took me weeks to debug the math. Eventually used a library but modified it for my joint constraints.\"\n\n[Extract facts → append to user.md]\n- Struggled with inverse kinematics math, debugged and modified existing library\n\nQuestion 3: \"How does this hobby map to the type of work you want?\"\nUser: \"I want to work on practical, deployable robotics—not research. I like solving real engineering constraints, not publishing papers.\"\n\n[Extract facts → append to user.md]\n- Prefers practical/deployable robotics over research, enjoys engineering constraints\n\n[Draft new statements based on these 3 answers]\nMe: \"Here are 3 new draft statements based on your robotics work. Approve / Edit / Reject?\"\n\nStatement (Technical/proof-first):\n\"I've built 3 functional robotic arms from scratch using Arduino, custom Python kinematics, and 3D-printed components. My GitHub repo has been forked 40+ times, and I've published video demos on YouTube. I focus on practical, deployable solutions—not academic research.\"\nTags: #robotics #arduino #python #github #practical #hands-on\n\nUser: \"Approve.\"\n\n[Write to statements.md]\n\n[... continue ...]" }, { "title": "No Invented Achievements", "body": "Only write statements grounded in gathered facts\nIf user didn't mention it, don't make it up" }, { "title": "No Sensitive Data (Unless Explicit)", "body": "Don't include salary history, medical details, or private info unless user explicitly provides and approves it" }, { "title": "If User Requests Exaggeration or Fabrication", "body": "Refuse politely: \"I can't invent achievements, but I can help you frame what you've done more compellingly. Let's work with the real facts.\"\nOffer truthful alternatives" }, { "title": "Conflicts and Uncertainty", "body": "If something doesn't add up, note it in coherence.md and ask for clarification\nNever guess or fill in blanks" }, { "title": "Running as a Cron Job (Continuous Learning)", "body": "You can schedule this skill to run periodically (weekly, monthly) to continuously learn more about the person and build their statement library.\n\nExample cron job payload:\n\n{\n \"kind\": \"agentTurn\",\n \"message\": \"Run the proposal-interview skill for Mike. This is a continuation session (not first run), so ask 3 new questions, gather facts, draft 2-4 statements, and get approval. Focus on filling gaps in his profile or drilling deeper on OpenClaw implementation experience.\"\n}\n\nBenefits of cron-based learning:\n\nBuilds statement library over time without overwhelming the user\n3-question rounds keep sessions short and token-efficient\nCan be scheduled during low-activity periods\nGradually captures more depth and nuance\n\nImportant: Always use the 3-question pattern for cron sessions, never the initial 10-question onboarding." }, { "title": "Checklist: Every Run", "body": "⚠️ CRITICAL CHECKS - READ THESE EVERY TIME:\n\nBefore you start:\n\nHave I identified which person/company this is for?\n Have I read profile.md FIRST to get current context?\n Have I read existing user.md or org.md to see what facts are already captured?\n Have I read existing statements.md to avoid duplicating approved statements?\n Have I read preferences.md and coherence.md?\n Have I determined if this is a first run (10 questions) or continuation (3 questions)?\n\nDuring the interview:\n\nAm I asking questions that allow short or long replies?\n Am I reading existing facts BEFORE appending to avoid duplicates?\n Am I appending facts (NEVER deleting) to the correct file (user.md or org.md)?\n Am I noting conflicts in coherence.md instead of rewriting?\n Am I tagging statements with relevant keywords?\n\nWhen drafting statements:\n\nHave I read existing statements to avoid duplicates?\n Are all statements grounded in gathered facts?\n Have I written variants for relevant platforms (Upwork, cover letter, technical)?\n Have I asked: Approve / Edit / Reject for each statement?\n Have I appended approved statements (NEVER deleting old ones) to statements.md?\n Have I updated preferences.md based on user feedback?\n\nAfter the session:\n\nHave I noted any gaps or missing info in coherence.md?\n Have I identified categories that need more coverage for next round?\n Have I maintained the append-only rule (no deletions, only additions)?\n Did I update profile.md if any current information changed?" }, { "title": "Summary", "body": "This skill transforms generic proposals into personalized, compelling letters by:\n\nInterviewing you to extract unique, personal-but-professional facts\nDrafting reusable statements grounded in those facts\nRefining statements through an approval loop\nStoring approved statements for future assembly\n\nThe result: a library of high-quality, pre-approved statements you can mix and match for any proposal, tailored to the platform and company.\n\nNext steps:\n\nRun the onboarding + 10 initial questions\nApprove your first batch of statements\nRun 3-question rounds to fill gaps and drill down\nBuild a library of 20-50 statements covering different angles\n(Future) Use those statements to assemble custom proposals on demand\n\nFile locations:\n\nPersonal: skills/proposal-interview/personal//\nCompanies: skills/proposal-interview/companies//\nAlways append, never delete\nCheck coherence.md for gaps" } ], "body": "Proposal & Cover Letter Discovery Interview\n\nThis is NOT a CV builder. This skill creates high-quality, reusable statements for proposals and cover letters by running a structured interview to extract personal-but-professional facts.\n\nThe Problem with Generic Letters\n\nGeneric cover letter and proposal writers are bland because they don't know YOU. They can't capture:\n\nYour living in Dubai and Seoul, and what that taught you about cross-cultural collaboration\nThe robotics project you tinkered with at home that shows your passion\nThe class that changed how you think about systems\nThe boring job that taught you what quality really means\nYour unfair advantage that clients actually hire you for\n\nThis skill solves that through interview → facts → statements → approval → assembly.\n\nHow It Works\nPhase 1: Discovery Interview\n\nThe skill asks structured questions to extract:\n\nGeographic and cultural context (places lived, travel, cross-cultural work)\nWork experience beyond the resume (lessons, standout moments, what colleagues rely on you for)\nEducation (specific classes, formative learning, projects)\nProjects and proof (side projects, demos, artifacts)\nAwards and recognition (scholarships, competitions, certifications)\nPast hobbies (skills hidden in former interests)\nBooks and influences (working philosophy)\nThe boring stuff (what you learned from frustrating work)\nProposal leverage (what you want to be hired for)\nConstraints (topics to avoid, boundaries)\nPhase 2: Statement Generation\n\nFrom gathered facts, the skill drafts 3-8 candidate statements per round. Each statement:\n\nIs grounded in real facts (no invention)\nIs usable in proposals/cover letters\nHas multiple variants (Upwork short, standard cover letter, technical/proof-first)\nHas tags (#leadership #robotics #global-living)\nPhase 3: Approval Loop\n\nYou review each statement: Approve / Edit / Reject\n\nApproved statements go into statements.md\nEdits refine the statement and update preferences\nRejections inform future drafting\nPhase 4: Assembly (Future)\n\nWhen you need a proposal, the skill pulls relevant approved statements and assembles them for the target platform and company.\n\nStorage Model: Folders + Files\n\nAll data is stored INSIDE the skill folder at: skills/proposal-interview/personal/ and skills/proposal-interview/companies/\n\nDirectory Structure\nskills/proposal-interview/\n personal/\n /\n profile.md # Current snapshot: name, what they do, where, objectives (ALWAYS READ FIRST)\n user.md # Raw facts about this person (APPEND ONLY - NEVER DELETE)\n statements.md # Approved statements (APPEND ONLY - NEVER DELETE APPROVED STATEMENTS)\n preferences.md # Writing style preferences\n coherence.md # Conflicts, gaps, clarifications needed\n\n companies/\n /\n profile.md # Current snapshot: company name, what they do, where, objectives\n org.md # Company facts, domain, relationships (APPEND ONLY - NEVER DELETE)\n statements.md # Company-specific approved statements (APPEND ONLY - NEVER DELETE)\n preferences.md # Company-specific style preferences\n projects.md # (Optional) Project history with this org\n coherence.md # (Optional) Company-specific conflicts/gaps\n\nRouting Rules\n\nPersonal vs Company:\n\nPersonal facts → skills/proposal-interview/personal//user.md\nCompany-specific facts → skills/proposal-interview/companies//org.md\n\nMulti-person support:\n\nDefault: current user\nIf doing this for someone else (e.g., spouse), use skills/proposal-interview/personal//\n\nRelationships:\n\nIf a company has an owner/founder relevant to letters, record in org.md\nFile Rules (Append-Only)\n\n⚠️ CRITICAL FOR ALL MODELS - READ THIS:\n\nNEVER DELETE OR REWRITE LINES IN ANY FILE. ALWAYS APPEND. NEVER DELETE. ONLY ADD.\n\nThis applies to:\n\n❌ NEVER delete approved statements from statements.md\n❌ NEVER delete facts from user.md or org.md\n❌ NEVER rewrite existing lines\n✅ ALWAYS append new information\n✅ ALWAYS read existing files before appending\n\nIf a conflict is detected:\n\nAppend the new info (don't delete the old info)\nAppend a note to coherence.md\nAsk a clarifying question next round\n\nprofile.md is the EXCEPTION - this file CAN be edited/rewritten as it's a current snapshot, not a permanent record.\n\nprofile.md (personal or company) — ALWAYS READ FIRST\n\nCurrent snapshot of the person or company. Simple, clear, updated format.\n\nPersonal profile.md format:\n\n# [Full Name]\n\n## What They Do\n[Simple description - \"AI consultant specializing in OpenClaw implementations and AI strategy\"]\n\n## Where Based\n[Location - \"Amsterdam, Netherlands\" or \"Remote\" or \"San Francisco, CA\"]\n\n## Primary Objective\n[Main goal for proposals/applications - \"Secure OpenClaw implementation contracts with mid-size tech companies\"]\n\n## Secondary Objective (Optional)\n[Secondary goal - \"Build reputation as AI strategy consultant for startups\"]\n\n## Current Status\n[Brief context - \"Actively applying to Upwork projects and direct outreach to companies\"]\n\n## Last Updated\n[Date - \"2026-02-24\"]\n\n\nCompany profile.md format:\n\n# [Company Name]\n\n## What They Do\n[Simple description - \"Industrial automation, warehouse robotics\"]\n\n## Where Based\n[Location - \"San Francisco, CA\"]\n\n## Primary Relationship Objective\n[Why we're tracking them - \"Potential client for OpenClaw implementation\"]\n\n## Secondary Objective (Optional)\n[Additional context - \"Investor prospect for Way Back Project\"]\n\n## Key Contact\n[Name and role if known - \"Jane Doe, CTO\"]\n\n## Last Updated\n[Date - \"2026-02-24\"]\n\n\nWorkflow: Always read profile.md FIRST (before user.md, statements.md, etc.) to get current context.\n\nuser.md (personal) — ⚠️ APPEND ONLY, NEVER DELETE ⚠️\n\nCRITICAL REMINDER: Before writing to this file, ALWAYS read existing content first to avoid duplicates and incorporate existing facts.\n\nRaw facts and concise notes. Facts only, no polished marketing.\n\nExample:\n\n- Lived in Dubai 2018-2020, worked with clients across EMEA\n- Lived in South Korea 2015-2017, learned Korean to intermediate level\n- Built robotic arms at home using Arduino and 3D-printed parts\n- Took MIT OCW Machine Learning course, applied to personal project predicting stock trends\n- Won regional robotics competition in high school, team captain\n- Former competitive swimmer (stopped 2016), coached youth swim team 2017-2018\n- Speaks English (native), Korean (intermediate), Arabic (basic)\n- Prefers remote work, available 9am-5pm EST\n\nstatements.md (personal or company) — ⚠️ APPEND ONLY, NEVER DELETE APPROVED STATEMENTS ⚠️\n\nCRITICAL REMINDER: Once a statement is approved and written here, NEVER delete it. Only append new approved statements. Read existing statements before generating new ones to avoid duplicates.\n\nUser-approved statements only. Each entry includes:\n\nStatement text\nTags\nEvidence pointer (which facts support this)\n\nExample:\n\n---\nstatement: \"I bring a global perspective from living and working across three continents—from collaborating with EMEA clients in Dubai to navigating cross-cultural teams in South Korea. I've learned to adapt communication styles and build trust across cultures, which is essential for remote, distributed work.\"\ntags: #global-living #dubai #korea #cross-cultural #remote-work #client-facing\nevidence: user.md lines 1-2, 7\nplatform: standard cover letter\n---\n\nstatement: \"I'm passionate about robotics and hands-on engineering—I've built robotic arms at home using Arduino and 3D-printed custom parts. This isn't just work for me; it's how I spend my evenings.\"\ntags: #robotics #hands-on #passion #arduino #3d-printing #side-projects\nevidence: user.md line 3\nplatform: Upwork short pitch, technical/proof-first\n---\n\nstatement: \"My background in competitive swimming taught me discipline and coaching—skills I later applied when coaching a youth swim team. I understand how to break down complex skills, provide feedback, and build confidence.\"\ntags: #coaching #leadership #discipline #teaching #past-hobbies\nevidence: user.md line 6\nplatform: standard cover letter, leadership-focused\n---\n\npreferences.md (personal or company)\n\nWriting style preferences by platform.\n\nExample:\n\n# Writing Preferences\n\n## Tone\n- Confident but not arrogant\n- Warm and approachable\n- Direct, minimal fluff\n- Technical when relevant (show don't just tell)\n\n## Platform Settings\n\n### Upwork\n- Length: 2-4 sentences + optional 2-3 bullet proof points\n- Structure: Hook → proof → call-to-action\n- Metrics-first when available\n\n### LinkedIn / Email Outreach\n- Length: 3-5 sentences\n- Friendly, personal, brief\n- Lead with common ground or mutual connection\n\n### Job Portal / Formal Cover Letter\n- Length: 3-4 paragraphs\n- Structured: intro → experience/proof → why this role → close\n- Slightly more formal tone\n\n### Grants / Proposals\n- Length: longer, evidence-heavy\n- Structure: narrative with metrics and citations\n- Emphasize impact and outcomes\n\n## Avoid List\n- Buzzwords: \"synergy\", \"rockstar\", \"ninja\", \"guru\"\n- Overused phrases: \"I'm passionate about\", \"proven track record\"\n- Sensitive info: exact salary history, medical details\n\n## Structure Preferences\n- Prefer bullets for proof points\n- Use short paragraphs (3-4 sentences max)\n- Open with strongest differentiator\n- Close with clear next step\n\norg.md (company)\n\nCompany/initiative facts.\n\nExample:\n\n# Acme Robotics Inc\n\n## Domain\n- Industrial automation, warehouse robotics\n- Focus on AI-driven pick-and-place systems\n- Series B funded, 50-200 employees\n\n## Key People\n- Jane Doe, Founder/CEO (former Google engineer)\n- John Smith, CTO (robotics background)\n\n## Positioning\n- \"We make warehouses smarter\"\n- Emphasis on practical, deployable solutions (not research)\n\n## Constraints\n- Remote-first company\n- Looking for senior engineers with production experience\n\n## History with User\n- Applied via Upwork 2024-02-20\n- Initial call scheduled for 2024-02-28\n\ncoherence.md (optional but recommended)\n\nTrack conflicts, gaps, clarifications needed.\n\nExample:\n\n# Coherence Notes\n\n## Possible Conflicts\n- 2024-02-24: User said \"intermediate Korean\" but earlier mentioned \"basic conversational\". Clarify level.\n\n## Missing Info\n- Need timeframe for Dubai work (years? months?)\n- Need scope/metrics for robotics project (how many built? any demos?)\n- Need GPA or honors for MIT OCW course mention\n\n## Clarifications Needed\n- Is Arabic \"basic\" = conversational or just tourist phrases?\n- Does \"remote work preference\" mean fully remote only, or hybrid OK?\n\nHow to Use This Skill\n⚠️ QUESTION CADENCE - VERY IMPORTANT ⚠️\n\nFirst time with a person (onboarding):\n\nAsk 10 initial discovery questions in one session\nThen generate first batch of statements\n\nAll subsequent sessions (updates/refinement):\n\nAsk only 3 questions per round\nThen generate statements from those 3 answers\nThis keeps sessions manageable and can run via cron for continuous learning\n\nWhy this matters: You can schedule this skill as a cron job to periodically learn more about the person (every week, every month, etc.). The 3-question pattern keeps token usage reasonable while continuously building your statement library.\n\nStarting Fresh (First Run)\n\nRead this skill document to understand the workflow\n\nCreate folder structure if it doesn't exist:\n\nmkdir -p skills/proposal-interview/personal/ skills/proposal-interview/companies\n\n\nCreate profile.md with current snapshot (name, what they do, where, objectives)\n\nExplain the process to the user: \"I'm going to ask you 10 onboarding questions to build your initial profile. After this first session, future updates will only ask 3 questions at a time to keep things manageable. This can even run on a schedule to continuously learn more about you.\"\n\nRun onboarding questions (see below)\n\nAsk the 10 initial discovery questions\n\nDraft 3-8 statements, get approval, store approved ones\n\nFuture sessions: switch to 3-question rounds\n\nContinuing Work (Existing User) — ⚠️ READ BEFORE WRITING ⚠️\n\nCRITICAL: Always read existing files BEFORE asking questions or appending facts. This prevents duplicates and helps you incorporate existing knowledge.\n\nRead existing files IN THIS ORDER:\n\nskills/proposal-interview/personal//profile.md (READ FIRST - current context)\nskills/proposal-interview/personal//user.md (facts gathered - NEVER DELETE, ONLY APPEND)\nskills/proposal-interview/personal//statements.md (approved statements - NEVER DELETE, ONLY APPEND)\nskills/proposal-interview/personal//preferences.md (style guide)\nskills/proposal-interview/personal//coherence.md (gaps/conflicts)\n\nAsk only 3 new questions (fill gaps, drill down on threads)\n\nAppend new facts to user.md (NEVER delete existing facts, always append)\n\nDraft 2-4 new statements based on new facts\n\nGet approval, append to statements.md (NEVER delete approved statements, always append)\n\nWorking with a Company/Initiative\n\nCreate company folder: skills/proposal-interview/companies//\n\nAsk company-specific questions:\n\nWhat do they do? Domain?\nKey people? Relationships?\nWhy is user interested?\nWhat's the user's angle/fit?\n\nStore company facts in org.md\n\nDraft company-specific statements (e.g., \"why I'm a fit for Acme Robotics\")\n\nStore in company's statements.md\n\nQuestion Cadence (Hard Requirement)\n\nFirst-ever run for a person:\n\nAsk exactly 10 questions before generating statements\n\nAfter first batch:\n\nAsk 3 questions per round\nGenerate statements\nGet feedback\nUpdate files\nRepeat\n\nIf user gives very short answers:\n\nComment briefly: \"That's shorter than ideal, but I can work with it.\"\nAsk a follow-up only if critical\nOnboarding Script (Always First)\n\nWhen starting with a new person, ask these setup questions:\n\n1. Who is this for?\n\n\"Are you creating this for yourself, or for someone else (e.g., spouse, client)?\"\n\nIf for someone else, create skills/proposal-interview/personal//\n2. Which platforms do you use?\n\n\"Which platforms do you apply through? Check all that apply:\n\nUpwork / Freelance marketplaces\nLinkedIn (applications or outreach)\nEmail outreach (cold/warm)\nCompany career portals\nGrants / funding applications\nOther (specify)\"\n3. Style preferences per platform\n\nFor each platform they checked, ask: \"For [platform], what's your preferred style?\n\nTone: confident / warm / direct / humble / technical / playful / formal\nLength: short (2-4 sentences) / medium (1-2 paragraphs) / long (3-4 paragraphs)\nStructure: bullets / narrative / metrics-first / story-first\nWhat does success look like? (get a reply / win a contract / advance to interview)\"\n4. What do you want to be hired for?\n\n\"What type of work do you want more of? What's your unfair advantage?\"\n\n5. Anything to avoid?\n\n\"Any topics, buzzwords, or sensitive info we should avoid in proposals?\"\n\nAfter onboarding, write preferences to skills/proposal-interview/personal//preferences.md.\n\nThe 10 Initial Questions (Template)\n\nAfter onboarding, ask these 10 questions (adapt based on their work/goals):\n\n1. Geographic & Cultural Context\n\n\"Where have you lived or traveled that shaped how you work? (Dubai, Seoul, remote teams, etc.) Answer in 3 bullets or a short paragraph.\"\n\n2. Work Beyond the Resume\n\n\"What have you learned in your work that doesn't fit neatly on a resume? What was surprisingly hard and how did you handle it?\"\n\n3. What Colleagues Rely On You For\n\n\"What do colleagues, clients, or teammates repeatedly come to you for? What's your 'thing'?\"\n\n4. Education & Formative Learning\n\n\"Any classes, courses, or learning experiences that changed how you think or work? (Formal or self-taught—include MOOCs, bootcamps, workshops.)\"\n\n5. Projects & Proof\n\n\"What's a project you're proud of that shows your skills? (Side project, work project, personal tinkering, GitHub repo, portfolio piece.) Describe scope and outcome.\"\n\n6. Awards & Recognition\n\n\"Any awards, scholarships, competitions, certifications, or public recognition? (School, work, industry, community.)\"\n\n7. Past Hobbies\n\n\"What hobbies did you used to do a lot but don't anymore? What skills did they build? (Sports, arts, teaching, community involvement, etc.)\"\n\n8. Books & Influences (Optional)\n\n\"Any books, ideas, or people that shaped your approach to work or leadership? (Use sparingly, only if it produces something concrete.)\"\n\n9. The Boring Story\n\n\"Tell me about a role, class, or project you found boring or frustrating. What did you learn? What do you now avoid or demand in your work?\"\n\n10. Your Unfair Advantage\n\n\"If you had to pitch yourself in one sentence, what's your unfair advantage? What makes you different from 100 other people with similar skills?\"\n\nAfter these 10 questions:\n\nExtract facts → append to user.md\nDraft 3-8 statements (see below)\nGet approval\nStore approved statements → statements.md\nUpdate preferences.md based on feedback\nThe 3-Question Round (Subsequent Runs)\n\nAfter the initial 10 questions, switch to asking 3 questions per round.\n\nHow to choose the next 3 questions:\n\nCheck coherence.md for gaps or conflicts that need clarification\nReview statements.md to see which categories are under-represented\nDrill down on strong threads:\nIf user mentioned robots → ask about tools, scope, outcomes, demos\nIf user mentioned Dubai/Korea → ask about cross-cultural teamwork, languages, client communication\nIf user mentioned a specific company → ask domain-specific questions\n\nQuestion design principles:\n\nAllow short or long replies\nUse phrasing like: \"Answer in 3 bullets or a short paragraph.\"\nIf dates/metrics uncertain: \"Approximate is fine.\"\nAlways explain why it matters (briefly): \"This helps me write more personal proposals.\"\n\nAfter each 3-question round:\n\nExtract facts → append to user.md or org.md\nDraft 2-4 new statements\nGet approval\nUpdate files\nStatement Drafting + Approval Loop\nWhen to Draft Statements\nAfter the first 10 questions (initial run)\nAfter every 3-question round (subsequent runs)\nHow to Draft Statements\n\nGenerate 3-8 candidate statements per round.\n\nEach statement must:\n\nBe grounded in gathered facts (no invention)\nBe usable in proposals/cover letters\nBe written in multiple variants when helpful:\nUpwork short pitch (1-2 lines)\nStandard cover letter (2-4 sentences)\nTechnical/proof-first variant (metrics, tools, outcomes)\n\nStatement structure:\n\n---\nstatement: \"[The actual statement text]\"\ntags: #tag1 #tag2 #tag3\nevidence: user.md line X, org.md line Y\nplatform: Upwork short / standard cover letter / technical\n---\n\nApproval Process\n\nFor each statement, ask the user:\n\n\"Here's a draft statement. Choose one:\n\nApprove - Store as-is\nEdit - Suggest changes (I'll rewrite and confirm)\nReject - Don't store, move on\"\n\nIf user chooses Edit:\n\nPropose a rewrite\nGet confirmation\nIf confirmed, store\n\nIf user chooses Approve:\n\nRead existing statements.md first to avoid duplicates\nAppend the approved statement to statements.md in the correct folder (skills/proposal-interview/personal/ or skills/proposal-interview/companies/)\nNEVER delete previously approved statements\n\nIf user chooses Reject:\n\nDon't store (obviously, since it's rejected)\nNote the rejection reason in preferences.md if it reveals a style preference\n\n⚠️ CRITICAL REMINDER: Once a statement is approved and appended to statements.md, it must NEVER be deleted. Only append new approved statements.\n\nUpdate Preferences Based on Feedback\n\nAfter each approval round, update preferences.md if you learn:\n\nTone preferences (user prefers \"confident\" over \"humble\")\nLength preferences (user always wants shorter)\nStructure preferences (user likes bullets over narrative)\nWord choice (user hates \"passionate\", prefers \"focused on\")\nPlatform-Aware Statement Variants\nUpwork Short Pitch (2-4 sentences + bullets)\n\nExample:\n\nI've built robotic arms at home using Arduino and 3D-printed parts—this isn't just work for me, it's how I spend my evenings. I bring 5 years of experience with ROS, Python, and mechatronics, plus a global perspective from working with EMEA and APAC clients.\n\n• Built 3 functional robotic arms with custom inverse kinematics\n• MIT OCW Machine Learning graduate (applied to robotics path planning)\n• Available for 20-30 hrs/week, overlap with US/EU time zones\n\nStandard Cover Letter (2-4 sentences)\n\nExample:\n\nI bring a global perspective from living and working across three continents—from collaborating with EMEA clients in Dubai to navigating cross-cultural teams in South Korea. I've learned to adapt communication styles and build trust across cultures, which is essential for remote, distributed work. My technical background in robotics and hands-on engineering complements my ability to work with diverse teams and deliver practical solutions.\n\nTechnical / Proof-First Variant\n\nExample:\n\nI've designed and built three functional robotic arms using Arduino, custom inverse kinematics algorithms (Python), and 3D-printed components. I completed MIT OCW's Machine Learning course and applied it to a path-planning optimization project that reduced movement time by 18%. My GitHub portfolio includes ROS packages, simulation environments (Gazebo), and documentation that's been forked 40+ times.\n\nEmail Outreach (3-5 sentences, friendly)\n\nExample:\n\nHi [Name],\n\nI noticed Acme Robotics is hiring for a Senior Robotics Engineer. I've been tinkering with robotic arms at home for years—building them from scratch using Arduino and 3D-printed parts—and I'd love to bring that hands-on passion to a team working on real-world automation challenges.\n\nI've worked with clients across Dubai and South Korea, so I'm comfortable with remote collaboration and adapting to different working styles. Would you be open to a quick call to discuss the role?\n\nBest,\n[User]\n\nGrant / Long Proposal (Evidence-heavy, structured)\n\nExample:\n\nMy unique combination of hands-on robotics experience and cross-cultural collaboration positions me well for this initiative. Over the past four years, I have:\n\n1. **Designed and built functional robotic systems**: I independently developed three robotic arms using Arduino microcontrollers, custom inverse kinematics algorithms (Python), and 3D-printed mechanical components. These projects demonstrate my ability to work across hardware, software, and mechanical design.\n\n2. **Applied machine learning to robotics**: I completed MIT OpenCourseWare's Machine Learning curriculum and applied those techniques to optimize path planning for robotic arm movement, achieving an 18% reduction in task completion time.\n\n3. **Collaborated across cultures and time zones**: My professional experience spans Dubai (EMEA clients) and South Korea (APAC teams), where I learned to navigate language barriers, cultural differences, and asynchronous communication. I speak English natively, Korean at an intermediate level, and basic Arabic.\n\nThis background enables me to contribute both technical expertise and the adaptability required for distributed, international teams.\n\nAdaptive Question Generation\nHow to Decide What to Ask Next\n\nMaintain an internal checklist of what categories are covered:\n\n Geographic / cultural context\n Work experience beyond resume\n Education / formative learning\n Projects / proof\n Awards / recognition\n Past hobbies\n Books / influences\n Boring stories / frustrations\n Proposal leverage / unfair advantage\n Constraints / boundaries\n\nPrioritize questions that:\n\nFill gaps in under-represented categories\nDrill down on strong signals (unique experiences like living abroad)\nProduce demonstrable proof (projects, metrics, artifacts)\nAlign to target work (if a company/initiative is provided)\nTriggered Recall Questions\n\nIf user mentions robots:\n\n\"What tools did you use? What was the scope? Any metrics or demos?\"\n\"What's sitting in your office/workshop right now? How does it map to client value?\"\n\nIf user mentions Dubai/Korea:\n\n\"Tell me about a time cross-cultural communication was challenging. How did you adapt?\"\n\"What languages do you speak? At what level?\"\n\"How did living there change your approach to remote work or global clients?\"\n\nIf user mentions a specific job/company:\n\nPrioritize questions that produce domain-aligned statements\nStore company-specific learnings in skills/proposal-interview/companies//\nFact Capture Rules (Very Explicit) — ⚠️ READ THEN APPEND ⚠️\n\nCRITICAL WORKFLOW - DO THIS EVERY TIME:\n\nBEFORE appending any facts:\n\nREAD the existing user.md or org.md file to check what's already captured\nCheck for duplicates - don't re-add facts that are already there\nIncorporate existing facts when generating statements\n\nAfter each user answer:\n\nRead existing facts first (see above)\n\nExtract discrete factual lines from the answer\n\nAppend them to the correct file (NEVER delete existing content):\n\nPersonal facts → skills/proposal-interview/personal//user.md\nCompany facts → skills/proposal-interview/companies//org.md\n\nIf a fact is uncertain, ask a one-line confirmation before writing:\n\n\"You mentioned living in Dubai—was that 2018-2020, or different years?\"\n\nNever delete or rewrite previous lines. If a conflict is detected:\n\nAppend the new info (DO NOT DELETE THE OLD INFO)\nAppend a \"possible conflict\" note to coherence.md\nAsk a targeted clarifying question next round\n\nREMINDER: APPEND ONLY. NEVER DELETE. ALWAYS READ BEFORE WRITING.\n\nExample Session Flow\nSession 1: Onboarding + Initial 10 Questions\n[Onboarding]\nMe: \"Are you creating this for yourself, or for someone else?\"\nUser: \"For myself.\"\n\nMe: \"Which platforms do you apply through? Upwork, LinkedIn, email, job portals, grants?\"\nUser: \"Upwork and LinkedIn mostly.\"\n\nMe: \"For Upwork, what's your preferred style? Tone, length, structure?\"\nUser: \"Confident but not cocky, short (2-4 sentences + bullets), metrics-first.\"\n\n[Preferences captured → write to preferences.md]\n\n[Initial 10 Questions]\nMe: \"Question 1: Where have you lived or traveled that shaped how you work?\"\nUser: \"I lived in Dubai for 2 years (2018-2020) and Seoul for 3 years (2015-2017). Dubai taught me how to work with clients across EMEA time zones. Korea taught me patience and indirect communication styles.\"\n\n[Extract facts → append to user.md]\n- Lived in Dubai 2018-2020, worked with EMEA clients\n- Lived in Seoul 2015-2017, learned indirect communication styles\n\nMe: \"Question 2: What have you learned that doesn't fit neatly on a resume?\"\nUser: \"I learned how to handle ambiguity. Clients don't always know what they want, and I've gotten good at asking clarifying questions early.\"\n\n[Extract facts → append to user.md]\n- Skilled at handling ambiguous client requirements, asks clarifying questions early\n\n[... continue through 10 questions ...]\n\n[After 10 questions: Draft statements]\nMe: \"Based on what you've shared, here are 5 draft statements. For each, tell me: Approve / Edit / Reject.\"\n\nStatement 1 (Upwork short):\n\"I bring a global perspective from living in Dubai and Seoul, where I collaborated with EMEA and APAC clients across time zones. I'm comfortable with remote work and cross-cultural communication.\"\nTags: #global-living #dubai #korea #remote-work #cross-cultural\n\nUser: \"Approve.\"\n\n[Write to statements.md]\n\nStatement 2 (Standard cover letter):\n\"I excel at navigating ambiguous client requirements. Early in projects, I ask targeted clarifying questions to uncover what clients really need—even when they don't know themselves yet.\"\nTags: #client-facing #ambiguity #discovery #consultative\n\nUser: \"Edit—sounds too soft. Make it more confident.\"\n\nMe: \"How about: 'I thrive in ambiguous situations. When clients aren't sure what they need, I ask the right questions upfront to define clear goals and avoid costly rework later.'\"\n\nUser: \"Perfect. Approve.\"\n\n[Write revised version to statements.md, update preferences.md: prefer confident tone]\n\n[... continue through all statements ...]\n\nSession 2: 3-Question Round\n[Read existing files: user.md, statements.md, preferences.md, coherence.md]\n\nMe: \"I see you mentioned robotics earlier. Let's drill down on that.\"\n\nQuestion 1: \"You said you built robotic arms at home. How many? What tools and frameworks? Any demos or GitHub repos?\"\nUser: \"I've built 3 so far. Arduino for controllers, Python for kinematics, 3D-printed the parts. I have videos on YouTube and code on GitHub—one repo has 40+ forks.\"\n\n[Extract facts → append to user.md]\n- Built 3 robotic arms at home: Arduino controllers, Python kinematics, 3D-printed parts\n- YouTube demos, GitHub repo with 40+ forks\n\nQuestion 2: \"What was the hardest part of building them?\"\nUser: \"Getting the inverse kinematics right. Took me weeks to debug the math. Eventually used a library but modified it for my joint constraints.\"\n\n[Extract facts → append to user.md]\n- Struggled with inverse kinematics math, debugged and modified existing library\n\nQuestion 3: \"How does this hobby map to the type of work you want?\"\nUser: \"I want to work on practical, deployable robotics—not research. I like solving real engineering constraints, not publishing papers.\"\n\n[Extract facts → append to user.md]\n- Prefers practical/deployable robotics over research, enjoys engineering constraints\n\n[Draft new statements based on these 3 answers]\nMe: \"Here are 3 new draft statements based on your robotics work. Approve / Edit / Reject?\"\n\nStatement (Technical/proof-first):\n\"I've built 3 functional robotic arms from scratch using Arduino, custom Python kinematics, and 3D-printed components. My GitHub repo has been forked 40+ times, and I've published video demos on YouTube. I focus on practical, deployable solutions—not academic research.\"\nTags: #robotics #arduino #python #github #practical #hands-on\n\nUser: \"Approve.\"\n\n[Write to statements.md]\n\n[... continue ...]\n\nSafety and Integrity\nNo Invented Achievements\nOnly write statements grounded in gathered facts\nIf user didn't mention it, don't make it up\nNo Sensitive Data (Unless Explicit)\nDon't include salary history, medical details, or private info unless user explicitly provides and approves it\nIf User Requests Exaggeration or Fabrication\nRefuse politely: \"I can't invent achievements, but I can help you frame what you've done more compellingly. Let's work with the real facts.\"\nOffer truthful alternatives\nConflicts and Uncertainty\nIf something doesn't add up, note it in coherence.md and ask for clarification\nNever guess or fill in blanks\nRunning as a Cron Job (Continuous Learning)\n\nYou can schedule this skill to run periodically (weekly, monthly) to continuously learn more about the person and build their statement library.\n\nExample cron job payload:\n\n{\n \"kind\": \"agentTurn\",\n \"message\": \"Run the proposal-interview skill for Mike. This is a continuation session (not first run), so ask 3 new questions, gather facts, draft 2-4 statements, and get approval. Focus on filling gaps in his profile or drilling deeper on OpenClaw implementation experience.\"\n}\n\n\nBenefits of cron-based learning:\n\nBuilds statement library over time without overwhelming the user\n3-question rounds keep sessions short and token-efficient\nCan be scheduled during low-activity periods\nGradually captures more depth and nuance\n\nImportant: Always use the 3-question pattern for cron sessions, never the initial 10-question onboarding.\n\nChecklist: Every Run\n\n⚠️ CRITICAL CHECKS - READ THESE EVERY TIME:\n\nBefore you start:\n\n Have I identified which person/company this is for?\n Have I read profile.md FIRST to get current context?\n Have I read existing user.md or org.md to see what facts are already captured?\n Have I read existing statements.md to avoid duplicating approved statements?\n Have I read preferences.md and coherence.md?\n Have I determined if this is a first run (10 questions) or continuation (3 questions)?\n\nDuring the interview:\n\n Am I asking questions that allow short or long replies?\n Am I reading existing facts BEFORE appending to avoid duplicates?\n Am I appending facts (NEVER deleting) to the correct file (user.md or org.md)?\n Am I noting conflicts in coherence.md instead of rewriting?\n Am I tagging statements with relevant keywords?\n\nWhen drafting statements:\n\n Have I read existing statements to avoid duplicates?\n Are all statements grounded in gathered facts?\n Have I written variants for relevant platforms (Upwork, cover letter, technical)?\n Have I asked: Approve / Edit / Reject for each statement?\n Have I appended approved statements (NEVER deleting old ones) to statements.md?\n Have I updated preferences.md based on user feedback?\n\nAfter the session:\n\n Have I noted any gaps or missing info in coherence.md?\n Have I identified categories that need more coverage for next round?\n Have I maintained the append-only rule (no deletions, only additions)?\n Did I update profile.md if any current information changed?\nSummary\n\nThis skill transforms generic proposals into personalized, compelling letters by:\n\nInterviewing you to extract unique, personal-but-professional facts\nDrafting reusable statements grounded in those facts\nRefining statements through an approval loop\nStoring approved statements for future assembly\n\nThe result: a library of high-quality, pre-approved statements you can mix and match for any proposal, tailored to the platform and company.\n\nNext steps:\n\nRun the onboarding + 10 initial questions\nApprove your first batch of statements\nRun 3-question rounds to fill gaps and drill down\nBuild a library of 20-50 statements covering different angles\n(Future) Use those statements to assemble custom proposals on demand\n\nFile locations:\n\nPersonal: skills/proposal-interview/personal//\nCompanies: skills/proposal-interview/companies//\nAlways append, never delete\nCheck coherence.md for gaps" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/drafthead/proposal-and-coverletter-interviewer-improver", "publisherUrl": "https://clawhub.ai/drafthead/proposal-and-coverletter-interviewer-improver", "owner": "drafthead", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/proposal-and-coverletter-interviewer-improver", "downloadUrl": "https://openagent3.xyz/downloads/proposal-and-coverletter-interviewer-improver", "agentUrl": "https://openagent3.xyz/skills/proposal-and-coverletter-interviewer-improver/agent", "manifestUrl": "https://openagent3.xyz/skills/proposal-and-coverletter-interviewer-improver/agent.json", "briefUrl": "https://openagent3.xyz/skills/proposal-and-coverletter-interviewer-improver/agent.md" } }