linkedin-store-post

name

linkedin-store-post

description

Store one or more already written, shared, or published LinkedIn items in the selected Ink profile corpus with deterministic filenames and the repo storage templates. Use when the user says things like "I shared this", "store this post", "store these posts", "store the following posts", "save this to the corpus", "add these to the corpus", "log this LinkedIn post", "import these posts", or provides multiple posts separated by `|`, especially when the content already exists and should be written into the selected profile's LinkedIn root with the correct format, date, follow-up number, and optional format-template metadata. Do not use this skill for drafting new copy or for final review before approval.

LinkedIn Store Post

Use this to log content that was already shared.

Resolve the active Ink profile before writing local files or creating One Horizon records. If multiple profiles exist and none is named, ask which profile to use.

Defaults

• default format to post unless the user says otherwise
• default published_at to today if the user gives no date
• default format_template to default-post for posts unless another template is named
• derive the title from the opening line if the user does not provide one

Intent Contract

• Use this skill when the primary user intent is storage, logging, saving, importing, or adding existing LinkedIn content to the corpus.
• Do not switch to the drafting workflow just because the stored content is pasted inline.
• Do not use linkedin-finalize-post unless the user also wants a final review pass before storage.

Examples that should route here:

• Store this post:
• Store the following posts:
• Store the following posts (separated by |):
• Add these LinkedIn posts to the corpus
• Log these posts from this week

Ask only if needed

Ask only when the storage would be misleading without the answer.

High-value questions:

• Was this a post, comment reply, DM, DM reply, or repost?
• Was this shared today, or on another date?
• Which format template did this follow, if any?

If the user only says "I shared this:" and gives text, store it as a post for today.

Batch Input

• If the user provides multiple posts separated by |, split on |, trim whitespace, and ignore empty items.
• Store each post as a separate corpus entry in input order.
• Apply shared defaults for format, published_at, and format_template unless the user gives per-item metadata.
• Do not merge multiple posts into one file.

Read

• ../linkedin-social-writer/references/corpus-spec.md
• ../linkedin-social-writer/templates/README.md
• ../linkedin-social-writer/templates/formats/README.md

Write path

Single post:

python3 .agents/linkedin-social-writer/scripts/store_published.py --profile <profileId> --body "..."

Multiple posts (batch):

Write all posts to a temporary file separated by | (or --- for multi-line posts), then call:

python3 .agents/linkedin-social-writer/scripts/store_published_batch.py \
  --profile <profileId> \
  --posts-file /tmp/posts.txt \
  [--separator "|"] \
  [--format post] \
  [--published-at YYYY-MM-DD]

The batch script accepts the same metadata flags as store_published.py and applies them to every post in the file. It prints one stored path per post and a summary line at the end.

Do not handcraft filenames or file bodies manually when the scripts can do it.

One Horizon: Record Published Post

After each selected-profile local corpus write succeeds, use the One Horizon MCP to create a child initiative under Ink - LinkedIn in the selected profile workspace.

Before mutating One Horizon, read ../one-horizon-context-setup/references/ink-initiative-hierarchy.md.

Fields:

• Title: the post title or the first 60 characters of the opening line
• Description: format, published date, and the local corpus path
• Status: Completed
• Parent: Ink - LinkedIn via parentInitiativeId

Rules:

• Create one One Horizon record per stored post, not one record for the whole batch.
• If a matching LinkedIn initiative already exists and is missing the Ink - LinkedIn parent or is under a different parent, move it with update_initiative before updating or reporting it.
• If the One Horizon MCP is unavailable, log the corpus path in the response and continue. Do not block storage on One Horizon availability.
• If the Ink - LinkedIn parent initiative does not exist, note that in the output and skip the One Horizon step for that item.

Output

Return:

• the saved corpus path for each stored item
• the One Horizon initiative title for each item where the record was created
• the assumptions used for date, format, or template