atlassian-attachments
Attach documents, screenshots, PDFs, and files to Jira issues and Confluence pages via REST API. Use when uploading evidence, documentation, or media to Atlassian products.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill atlassian-attachments53
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable code examples for Atlassian attachment operations, but suffers from severe verbosity and poor organization. The content is approximately 5x longer than necessary, with redundant examples, tables of information Claude already knows (file extensions, basic concepts), and no progressive disclosure structure. The core value is buried in excessive detail.
Suggestions
Reduce to ~100-150 lines by removing redundant examples (keep one curl + one Python example per operation), eliminating file type tables, and condensing authentication setup to a single code block
Split into multiple files: SKILL.md (quick reference), CONFLUENCE-EMBEDDING.md (the complex ri:attachment details), QA-MAPPING.md (screenshot naming conventions)
Add explicit validation steps to batch upload scripts: check response codes, report failures, provide retry guidance
Remove explanatory text like 'PDF (Portable Document Format)' patterns - assume Claude knows what file types are
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 600+ lines with significant redundancy. Multiple authentication setup sections, repeated curl/Python examples for similar operations, and extensive tables explaining file types Claude already knows. The QA screenshot mapping section alone is ~150 lines that could be condensed to 20. | 1 / 3 |
Actionability | Excellent executable examples throughout - complete curl commands, working Python functions, and bash scripts that are copy-paste ready. Includes specific headers, endpoints, and authentication patterns with real code. | 3 / 3 |
Workflow Clarity | Multi-step workflows exist (upload-and-embed) with some validation, but lacks explicit checkpoints for batch operations. The 'Upload All Test Evidence' script has no error handling or verification that uploads succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Content that should be split (QA mapping conventions, file type tables, macro reference) is all inline. No clear hierarchy between quick-start and advanced usage. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1041 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.