Postpeer Api

Organization

PostPeer-API

postpeer-api

Route PostPeer MCP and developer-reference work. Use when the user asks about PostPeer tools, postpeer.dev, MCP, REST or OpenAPI schemas, TypeScript SDK usage, platform prerequisites, authentication architecture, or low-level tool routing. For live publishing, connections, analytics, and notifications, use the bundled PostPeer MCP tools and prefer the focused PostPeer skills.

Overview

Publisher	PostPeer-API
Repository	`skills`
Skill name	`postpeer-api`
Stars	73
Forks	1
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by PostPeer-API on GitHub. Read the source before you install it.

Installation

Install the Postpeer Api AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/PostPeer-API/skills/tree/main/skills/postpeer-api
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/PostPeer-API/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/postpeer-api .claude/skills/postpeer-api

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Postpeer Api in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Postpeer Api on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Postpeer Api is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

PostPeer API

Execution Boundary

Use the bundled PostPeer MCP server for every live PostPeer operation. Its access key is collected in the plugin configuration UI and passed securely to the declared server.

Do not look for credentials in shell configuration, local files, or process state.
Do not ask the user to paste an access key into chat.
Do not make authenticated REST requests or launch a local MCP package.
If the MCP server is unavailable or authentication fails, explain how to update the plugin's PostPeer API key in Claude's plugin configuration UI, then stop the live operation.

REST, SDK, and OpenAPI information may be discussed when the user is building their own integration. Treat it as developer reference, not as this plugin's execution path. The OpenAPI source of truth is https://api.postpeer.dev/documentation/json.

MCP Tool Routing

The names below are exposed by PostPeer's hosted MCP documentation and implementation:

Posts: create_post, list_posts, get_post, delete_post.
Scheduling: list_scheduled_posts, cancel_scheduled_post, reschedule_post.
Connections: get_oauth_url, connect_bluesky, list_integrations, disconnect_integration.
Profiles: create_profile, list_profiles, get_profile, update_profile, delete_profile.
Analytics: get_analytics and the platform-specific analytics tools returned by the server.
Platforms: list_platforms, get_pinterest_boards, get_tiktok_creator_info, and other platform helpers returned by the server.
Media: create_media_upload, plus media-management tools returned by the server.
AI helpers: ai_write_content, ai_generate_image.
BYOK apps: create_app, list_apps, get_app, update_app, delete_app.
Notifications: test_notification, create_notification, list_notifications, get_notification, update_notification, delete_notification.

When a capability is not listed here, discover it from the connected PostPeer server instead of inventing a tool name or request shape.

Hard Rules

Set one delivery intent: saveAsDraft: true, publishNow: true, or scheduledFor plus timezone.
Use create_media_upload only for local media that needs a public URL. Skip it when the asset already has a public URL.
TikTok requires get_tiktok_creator_info before publishing. Use a returned privacyLevelOptions value and respect disabled comment, duet, and stitch flags.
Pinterest requires get_pinterest_boards; pass the selected boardId in platformSpecificData.
Use profiles to group integrations by end user, customer, or workspace.
Prefer notifications over repeated polling for publish lifecycle events.
Do not invent platform-specific fields. Discover them from PostPeer helpers or current documentation.
Cancel queued posts with cancel_scheduled_post; delete post records with delete_post.
Confirm publishing, deleting, disconnecting, webhook creation or tests, recipient changes, and other external changes unless the user's explicit request already provides the target and intended change.

Output Standards

State which PostPeer MCP tools were used.
Include IDs needed for follow-up operations.
Call out platform prerequisites and user action required for OAuth.
Never expose access keys, social credentials, webhook secrets, or other sensitive values.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Postpeer Api AI skill do?

Why use Postpeer Api on TypingMind?

Because you install it once and use it with any model. Postpeer Api is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Postpeer Api in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/PostPeer-API/skills/tree/main/skills/postpeer-api. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Postpeer Api?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Postpeer Api?

As many as you like. As long as a model supports skills, you can use Postpeer Api with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Postpeer Api AI skill free?

Yes. It is published on GitHub by PostPeer-API under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

PostPeer API

Execution Boundary

MCP Tool Routing

Hard Rules

Output Standards

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now