Instagram platform integration. Post content, manage stories, view insights, and engage with followers.
43
45%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/instagram/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is reasonably strong with specific actions and a clear platform niche (Instagram), making it distinctive. However, it lacks an explicit 'Use when...' clause, which weakens its completeness for skill selection. Adding trigger guidance and a few more natural keyword variations would improve it.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about posting to Instagram, managing IG stories, checking Instagram analytics, or interacting with Instagram followers.'
Include additional natural trigger terms users might say, such as 'reels', 'IG', 'social media posting', 'Instagram analytics', or 'DMs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Post content, manage stories, view insights, and engage with followers.' These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes 'Instagram', 'stories', 'insights', 'followers', and 'post content' which are relevant keywords, but misses common variations like 'reels', 'DMs', 'social media', 'IG', or file/API-related terms users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of 'Instagram platform integration' creates a clear niche. It is unlikely to conflict with other social media skills (e.g., Twitter, Facebook) due to the platform-specific naming. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder or stub—it lists features and provides a setup step for an access token, but offers zero actionable guidance on how to actually interact with the Instagram API. There are no API endpoints, no executable code examples, no error handling, and no workflows. It fails to teach Claude anything it couldn't already infer from the skill's title.
Suggestions
Add concrete, executable code examples showing actual Instagram Graph API calls (e.g., posting a photo via `POST /{ig-user-id}/media` with specific parameters and authentication headers).
Define step-by-step workflows for key operations like posting content (create media container → publish → verify) with validation checkpoints.
Include specific API endpoint references, required parameters, expected response formats, and error handling guidance for each listed feature.
Either remove the feature bullet list or replace it with actionable sections that each contain real implementation details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief, but the feature bullet list and usage examples are vague filler that don't add actionable value. The skill doesn't explain concepts Claude already knows, but it also doesn't earn its tokens with useful information. | 2 / 3 |
Actionability | There is no concrete code, no API endpoints, no executable commands, and no specific guidance on how to actually post photos, manage stories, or retrieve insights. The usage examples are just natural language prompts with no implementation details. | 1 / 3 |
Workflow Clarity | There are no multi-step processes defined, no sequences, and no validation checkpoints. The skill provides no workflow for any of the listed features—just a feature list and vague usage prompts. | 1 / 3 |
Progressive Disclosure | The content is short and organized into sections, which is fine for a simple skill. However, there are no references to supporting files and no bundle files exist, so the skill is essentially a stub with no depth to disclose progressively. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
f45fcb5
Table of Contents
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.