القائمة
Generate tailored Upwork proposals from job postings. 6-phase pipeline. Triggers: "write proposal", "proposal for", "upwork proposal", "generate proposal".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Scan repos for post-worthy code patterns, architectural decisions, bugs, and implementation insights. Produces structured insight briefs. Triggers: "mine code", "scan repos", "find insights", "what have we built".
Iterative scoring loop for post drafts. Evaluate on 5 criteria, fix weak areas, re-score until all criteria hit 8+. Max 5 iterations. Triggers: "score this post", "10/10", "rate this draft", "is this good enough".
Use when generating a post, creating content, or finding insights from code. Triggers: "generate post", "create content", "draft a post", "find insights". 7-phase structured content development. No draft before Phase 5.
Apply copywriting frameworks to post drafts. PAS, AIDA, BAB, 4Ps, StoryBrand. Triggers: "apply framework", "structure the post", "which framework". Includes anti-AI writing constraints applied during drafting, not after.
3-pass humanization for post drafts. Detects AI patterns, rewrites, then runs final checks (Coffee, Template, Scroll, AI Detector tests). Triggers: "humanize", "make it sound human", "ralph wiggum", "AI check".
استنادا إلى تصنيف SOC المهني
| name | proposal-pipeline |
| description | Generate tailored Upwork proposals from job postings. 6-phase pipeline. Triggers: "write proposal", "proposal for", "upwork proposal", "generate proposal". |
| user-invocable | true |
MANDATORY: Follow all 6 phases in order. No draft before Phase 5. No delivery before Phase 6 passes.
This skill uses its own rules, not the social media rules in .claude/rules/. Proposals are private 1-to-1 communication, not public content. The content pipeline rules (opening under 10 words, specific numbers from source code, depth requirements, no org names in proof URLs) do not apply here.
Parse the pasted job posting. Extract and present:
Match job keywords to determine which pillar to use:
| Job Keywords | Pillar | Voice |
|---|---|---|
| polymarket, kalshi, prediction market, trading bot, market making, DeFi, crypto trading | Polymaxr | Data-driven, precise, crypto-native. Numbers over narratives. Risk-aware and honest. |
| AI agent, Claude, chatbot, automation, LLM, RAG, OpenAI, prompt engineering, openclaw, moltbot | AIIn60 | Professional but approachable. Educational, not salesy. Practical and action-oriented. |
| Mixed (both categories) | Lead with the dominant pillar, mention the other | Blend both voices |
| Neither (general dev work) | Default to AIIn60 | Professional, practical |
Present the structured brief and pillar assignment. Get user confirmation before proceeding.
Evaluate the client using signals visible in the posting text. Read knowledge/client-signals.md for the full guide.
Check for:
Assign priority:
| Priority | Criteria |
|---|---|
| HIGH | Clear scope + verified payment + budget > $5K + our niche |
| MEDIUM | Good client + decent budget + close to our niche |
| LOW | Unclear scope OR budget concerns OR outside expertise |
| SKIP | Red flags OR deal breakers OR < $1.5K budget |
If SKIP: explain why and stop. Don't write proposals for bad-fit jobs.
Present assessment to user. Proceed on approval.
Read knowledge/portfolio.md and knowledge/proof-assets.md.
knowledge/pricing.md): What's the appropriate rate/package for this job's scope?Present the mapping to user:
Get approval before designing the proposal.
Select a copywriting framework based on the job type:
| Job Type | Framework | Why |
|---|---|---|
| Client has a clear pain point | PAS (Problem, Agitate, Solution) | Lead with their pain, show you understand it, present your fix |
| Client wants a transformation | BAB (Before, After, Bridge) | Show where they are, where they could be, how you get them there |
| Default / mixed | AIDA (Attention, Interest, Desire, Action) | Hook them, build interest with proof, create desire, close with CTA |
Outline all 7 Winning Patterns with specific planned content:
Present the outline. Do NOT draft until the user approves the design.
Write the proposal following the approved design from Phase 4.
Pattern 1: Opening Hook Open with an immediate credibility claim tied to the client's specific problem. Not a generic intro.
Pattern 2: Lead Portfolio Project Present the single most relevant past project. Include technical specifics that mirror what the client needs. Name the project, describe what it does, highlight the overlap with their requirements.
Pattern 3: Live Proof Include at least 2 proof links. Non-negotiable. Pick the most relevant from the approved list. Use raw URLs only.
Pattern 4: Current Relevance Show this is daily work, not a one-off. Use present tense: "I am currently building...", "I am actively running...", "I operate this daily..."
Pattern 5: Scope / Approach Show you understand THEIR specific problem. Outline 3-6 concrete deliverables using unicode bullets. Mirror the client's language and requirements from their job posting.
Pattern 6: CTA with Timeline Close with a specific deliverable and timeframe. Not vague.
Pattern 7: Voice First person ("I am", "I have", "I will"). Confident but not arrogant. No filler words. No buzzwords. Sign off as "Best regards, Sami".
Apply these WHILE drafting, not after:
**bold**, *italic*, __underline__.• instead of - or *.Dispatch the proposal-reviewer agent.
The reviewer checks:
If verdict is NEEDS WORK:
If verdict is APPROVED, deliver:
=== Proposal (Ready to Paste) ===
[plain text proposal]
=== Metadata ===
Pillar: [AIIn60 | Polymaxr]
Word count: [N]/280
Proof assets: [URLs used]
Priority: [HIGH | MEDIUM | LOW]
knowledge/proof-assets.md.