---
name: professional-network-outreach
description: "Reconcile relationship status and prepare relevant professional-network follow-ups. Use when the user requests professional network outreach. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.1"
---

# Professional Network Outreach

Reconcile relationship status and prepare relevant professional-network follow-ups.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Approved prospect list
- Relationship observations
- Message history
- Channel policy

## Methods

### Verify relationship state

Distinguish invited, connected and messaged states from direct observations; a profile match alone does not prove a connection or reply.

### Reconcile recent activity

Reconcile recent activity before proposing another action. Avoid duplicates and channel collisions with existing outreach or an active opportunity.

### Draft relevant messages

Draft specific, useful messages based on approved business context. Do not infer sensitive personal traits or invent a prior relationship.

### Return the review queue

Return a review queue with evidence, proposed next action and freshness. Sending invitations or messages requires authorization and current platform limits, never a copied daily quota.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.

## Additional operational methods

Read [focused operational guidance](references/relationship-reconciliation.md) for professional network outreach decisions that require deeper reconciliation.