← Job Outreach CopilotCONTENT HISTORY

Update to Job Outreach Copilot

Snapshot Nov 4, 2026 · 00:14 UTC · version 0.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Job Outreach Copilot and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Write first-contact LinkedIn invitation notes or DMs using correct channel rules.",
  "included_files": [],
  "name": "linkedin-outreach",
  "skill_md_contents": "---\nname: linkedin-outreach\ndescription: Write first-contact LinkedIn invitation notes or DMs using correct channel rules.\n---\n\n# Linkedin Outreach\n\n## When to use\nWrite first-contact LinkedIn invitation notes or DMs using correct channel rules. Do not trigger unrelated skills or assume the user wants outreach merely because they are discussing a job.\n\n## Required inputs\nVerified profile/post, connection degree or prior thread, candidate and opportunity. Use existing conversation evidence first, and ask only for an actual blocker; do not request repeated resume uploads if already available.\n\n## Workflow\nCheck Connect availability, invitation instructions, current relationship and earlier messages. Default to invitation note when possible; DM only when requested or existing thread. Short, human and evidence-based. Keep candidate facts, job-source facts, and conversation facts separate. When external facts matter, use current authorized tools or say clearly what could not be verified. Read `../../references/linkedin-channel.md` before acting.\n\n## Safety and approval\nNever invent candidate achievements, contact details, recruiter responses or job availability. Research and drafting are not authority to send, apply, submit a resume, agree to RTR, or modify external accounts. Request the appropriate explicit approval before consequential actions; report real receipts only. For multiple candidates, isolate profiles and data with candidate_id. Read `../../references/end-to-end-operating-model.md` and `../../references/candidate-isolation.md` for cross-skill rules.\n\n## Deliverable\nCopy-ready channel-specific text, never a sent claim. State clearly whether any research, draft, sent action, application or scheduled step was actually completed. If a critical verification was impossible, mark it as unverified rather than guessing.\n"
}

SHA-256 of public snapshot: 5971b448ef1333851661c3c852fb4425c02f0ab684584c492571c8cd020b791c