instagram-post
Post to Instagram with images, carousels, Reels, and Stories via Publora MCP (Business account required)
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/instagram-post/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly identifies specific capabilities (images, carousels, Reels, Stories) on a specific platform (Instagram) via a named tool (Publora MCP). Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are naturally what users would say, and the description is concise without being vague.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to post content to Instagram, schedule Instagram posts, share images/videos on Instagram, or create Instagram Reels or Stories.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: posting images, carousels, Reels, and Stories. Also specifies the platform (Instagram) and the tool (Publora MCP), plus a prerequisite (Business account required). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (post to Instagram with various content types via Publora MCP), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Instagram', 'images', 'carousels', 'Reels', 'Stories'. These are all terms users would naturally use when requesting Instagram posting functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Instagram posting via a specific tool (Publora MCP). The combination of platform, content types, and tool name makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionable guidance with concrete API examples, proper authentication details, and a useful REST API fallback. However, it's overly verbose with social media best practices and general knowledge that Claude already possesses, and it lacks an explicit multi-step workflow with validation checkpoints for the actual posting process (create → upload media → verify → publish).
Suggestions
Add an explicit numbered workflow for the complete posting process: create post → get upload URL → upload media → verify upload success → confirm post status, with validation at each step.
Remove or significantly trim the 'Best Practices' section (timing, engagement, hashtag strategy) as this is general social media knowledge Claude already knows.
Move the detailed platform limits tables and troubleshooting to a separate reference file (e.g., INSTAGRAM_LIMITS.md) and link to it from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is verbose in several areas. The 'Best Practices' section (engagement tips, timing advice, hashtag strategy) is general social media knowledge Claude already knows. The plan pricing table and some marketing-oriented content ('Best times: 11 AM - 1 PM') add tokens without much actionable value for the task of posting via API. | 2 / 3 |
Actionability | Provides concrete, executable code examples including full curl commands with proper headers, JSON configuration for MCP setup, and specific parameter details. The REST API fallback with complete request examples and the platform ID format explanation make this highly actionable and copy-paste ready. | 3 / 3 |
Workflow Clarity | The getting started steps are clearly sequenced, and the tool usage flow (create_post → get_upload_url → upload) is implied but not explicitly laid out as a numbered workflow with validation checkpoints. For a multi-step process involving media uploads and API calls, there's no explicit validate-then-proceed pattern or error recovery loop during the posting workflow itself. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections and tables, and references external docs (docs.publora.com). However, the file is quite long (~200+ lines) with detailed API limits, best practices, and troubleshooting all inline. The platform limits tables and best practices sections could be split into referenced files to keep the main skill leaner. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- publora/skills
- Commit
8e5bffe
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.