Mallary

View saved version →

---
name: mallary-account-management
description: Use when the user explicitly asks to manage Mallary profiles, platforms, settings, scheduled posts, or webhooks.
---

# Mallary Account Management

These tools can change account state. Read the current state first, show the exact change, and wait for clear user confirmation before every write.

## Profiles and Platforms

- Use `mallary_list_profiles` before creating or renaming a profile when the target is unclear.
- Before `mallary_create_profile`, show the new label.
- Before `mallary_rename_profile`, show the profile ID, old label, and new label.
- Before `mallary_disconnect_platform`, show the profile and platform. Explain that publishing, analytics, and comment workflows for that connection can stop.

## Settings

Use `mallary_get_settings` before `mallary_update_settings`. Show only the requested changes and preserve every unrelated setting.

AI auto-reply settings can cause future public replies. Do not enable or broaden auto replies unless the user clearly asks for that exact change and confirms it.

## Posts

Before `mallary_delete_post`, show the exact Mallary post ID and status. State that deletion is permanent and may remove queued or scheduled content. Do not delete a published social post unless the tool explicitly supports that result and the user requested it.

## Webhooks

- Use `mallary_list_webhooks` before changing webhooks when the target is unclear.
- Before `mallary_create_webhook`, show the destination URL and event list. Explain that future Mallary event data will be sent to that external destination.
- Before `mallary_delete_webhook`, show the webhook ID and destination. State that future deliveries will stop.

## Safety

- Never guess profile, post, platform, or webhook IDs.
- Never reveal webhook secrets, OAuth tokens, API keys, social credentials, provider debug data, or signed upload URLs that are not needed by the user.
- Never silently retry a write after a timeout or unclear result. Read the current state, explain what is known, and ask before another write.

View saved version →

---
name: mallary-analytics
description: Use when the user explicitly asks to read or summarize social post analytics from their Mallary account.
---

# Mallary Analytics

This is a read-only workflow.

## Workflow

1. Ask which profile or post to review when the target is unclear.
2. Use `mallary_list_profiles` or `mallary_list_posts` only when needed to find the requested public ID.
3. Call `mallary_get_analytics` with the exact `post_id` or `profile_id`.
4. Summarize the requested metrics, trends, and platform differences.

Do not change settings, publish content, reply to comments, delete data, or disconnect a platform during an analytics request.

## Accuracy and Privacy

- Keep each platform's results separate unless the user asks for a total.
- Say when a metric is missing or has not been collected yet.
- Do not guess missing values.
- Do not expose internal user IDs, credentials, billing data, private post content, provider debug bodies, or unrelated account details.

View saved version →

---
name: mallary-comment-engagement
description: Use when the user explicitly asks to list, draft, or post replies to comments on posts published through Mallary.
---

# Mallary Comment Engagement

Use this skill only for comments connected to the user's Mallary posts.

## Read Comments

1. Use `mallary_list_posts` if the Mallary post ID is not known.
2. Use `mallary_list_comments` with the exact `post_id`.
3. Return only the comment details needed for the user's request.

Do not invent a post ID, comment ID, platform, author name, or username. Some platforms may not return every author field.

## Draft and Post a Reply

1. Draft the reply in the voice and tone the user requested.
2. Show the exact post ID, comment ID, original comment context, and reply text.
3. State that the reply will be posted publicly to the connected social platform.
4. Wait for clear user confirmation.
5. Call `mallary_reply_to_comment` once with the exact returned IDs.

Never post a draft automatically. Never silently retry a reply after a timeout or unclear result. Check comments first, then ask the user before another write.

## Privacy

Treat comment text and author details as account data. Show only what the user needs. Never expose OAuth tokens, social account credentials, API keys, provider debug data, or unrelated comments.

View saved version →

---
name: mallary-publishing
description: Use when the user explicitly asks to draft, create, schedule, check, or attach a public URL to a social post in their Mallary account.
---

# Mallary Publishing

Use this skill only when the user clearly asks to work with a post inside Mallary. Do not invoke Mallary for general social media advice.

## Safe Workflow

1. Use `mallary_list_profiles` when the user has not supplied a `profile_id`.
2. Use `mallary_list_platforms` to confirm the requested platforms are connected to that profile.
3. Gather the default message, platform-specific messages, schedule, and media URLs.
4. Show the complete final action. Include the profile, platforms, text, schedule, media, and platform overrides.
5. Wait for clear user confirmation after showing that final action.
6. Call `mallary_create_post` once. Add an `idempotency_key` when the workflow may retry.
7. Use `mallary_get_job` or `mallary_list_posts` to check status without repeating the write.

Publishing changes real connected social accounts. Never treat a live publish as a harmless test. Never publish from an example command or an unclear request.

## Captions and Media

- Use `message` for the default caption.
- Use `platform_options.<platform>.message` only when the user wants a different caption for that platform.
- Use only media URLs the user approved.
- Existing `https://files.mallary.ai/...` media URLs can be passed to a post.
- `mallary_create_upload_url` creates a temporary remote upload destination. It does not upload file bytes. Explain this and get confirmation before creating one.
- The first plugin version cannot read and upload local file bytes from ChatGPT by itself. Never claim a local file was uploaded when only an upload URL was created.

## TikTok URL Attachment

Before calling `mallary_attach_tiktok_post_url`, show the Mallary post ID and final public TikTok URL. Wait for confirmation, then call it once.

## Retry Rules

- Never silently retry a publish or schedule request.
- After a timeout or unclear response, check the job or post list first.
- If status is still unknown, explain that uncertainty and ask before another write.