Skip to content
ownpost.Get OwnPost
ownpost-run-assistant4 min read

Complete queued assistant work

Claim one due preparation job, follow its saved brief and save its output back into OwnPost.

INSTALL THIS SKILL
npx skills@latest add https://github.com/zero-efforts/ownpost/tree/main/plugins/ownpost/skills --global --skill ownpost-run-assistant --agent codex

Requires access to the OwnPost repository. Installation and client options

When to use it

Use this skill in a connected client or its scheduler when OwnPost already has preparation work waiting. The assistant processes the due job to completion rather than simply explaining how to run it.

By default it claims at most one job. If there is no work, it creates no substitute task. A recurring run can remain quiet when there is nothing actionable.

What you need

A working MCP connection permitted to claim preparation work, a running client and a due preparation request. Preparation-only connections support this bounded workflow; ordinary draft writes are separate.

Install or select the skill

The ownpost entry skill includes this workflow. Use the command above if you want ownpost-run-assistant as a separate shortcut, or select it from your installed plugin.

Try it

Select the skill in your connected assistant, then adapt these examples to your own content.

Example requests
Use the ownpost-run-assistant skill to complete one due preparation job using its saved brief. Save the actual outputs; stay quiet if there is no work.

Use the ownpost-run-assistant skill to complete only the preparation occurrence selected in OwnPost and show me the saved draft links.

How it works

  1. Request one due job, or identify a particular occurrence. The assistant claims it and receives its task brief and a 30-minute lease.

  2. The assistant follows the saved sources, language, quantity and writing style. It reads selected Idea content when needed without changing the brief.

  3. For draft preparation, it writes the requested output, checks live length limits and completes the leased job with its outputs together. One job supports up to five drafts.

  4. Review the returned saved draft IDs and completed status in Assistant. A blocked active claim should be failed with a useful reason so you can resolve it.

  5. If you want recurring execution, configure the client’s scheduler separately and keep its runner available. Verify a later real check-in.

Generated preparation saves drafts. It does not publish to X. Ordinary writing requests use the posts workflow; leased preparation uses the selected job’s completion flow.

Check the result

The occurrence is completed and its result contains the saved draft IDs, or the assistant reports a concrete failure. No due work produces no substitute draft.

If something does not work

A copied prompt or saved key does not establish a working scheduler. If a completion response is uncertain, inspect the occurrence before retrying with the same lease. Expired or cancelled work cannot save output; repair the task state rather than creating unrelated drafts.

Skill source

RELATED GUIDES

Next steps

Use skills with your assistantScheduled preparationownpost-routinesownpost-postsOwnPost plugin