atlassian-rich-text-formatter

Generate Atlassian-ready rich text for Jira and Confluence from raw content or context. Use before creating or updating Jira descriptions, comments, environment fields, textarea custom fields, Confluence pages, blog posts, or comments when the endpoint needs ADF JSON, Jira wiki markup, Confluence storage XHTML, or Confluence wiki markup.

Quality

93%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Discovery

100%

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 an excellent skill description that clearly defines a specific niche (Atlassian rich text generation), lists concrete output formats and target contexts, and includes an explicit 'Use before...' trigger clause. It uses proper third-person voice and provides comprehensive trigger terms that would help Claude accurately select this skill from a large pool.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and outputs: 'Generate Atlassian-ready rich text for Jira and Confluence from raw content or context' and enumerates specific targets like Jira descriptions, comments, environment fields, textarea custom fields, Confluence pages, blog posts, and specific formats (ADF JSON, Jira wiki markup, Confluence storage XHTML, Confluence wiki markup).	3 / 3
Completeness	Clearly answers both 'what' (generate Atlassian-ready rich text in multiple formats) and 'when' (explicit 'Use before creating or updating...' clause with detailed trigger scenarios covering specific Jira and Confluence content types and format requirements).	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Jira', 'Confluence', 'ADF JSON', 'wiki markup', 'XHTML', 'rich text', 'Jira descriptions', 'comments', 'blog posts', 'Confluence pages'. These are terms users and Claude would naturally encounter when working with Atlassian products.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche focused specifically on Atlassian rich text formatting across multiple specific formats (ADF JSON, Jira wiki markup, Confluence storage XHTML, Confluence wiki markup). Unlikely to conflict with generic document or text processing skills due to the very specific Atlassian/Jira/Confluence domain.	3 / 3
	Total	12 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, concise skill that provides highly actionable format templates for all four Atlassian rich text formats. Its main strength is the concrete, executable examples for each format with proper wrapper structures. The primary weakness is the lack of validation guidance—there's no mention of checking ADF schema validity or XHTML well-formedness before submitting to APIs, which could lead to silent failures.

Suggestions

Add a brief validation note (e.g., 'Verify ADF has required version/type/content root keys and all nodes use valid types before returning') to improve workflow clarity for error-prone operations.

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It assumes Claude knows what ADF, wiki markup, and Confluence storage format are without explaining them. Every section provides only the structural templates and rules needed, with no padding or unnecessary context.	3 / 3
Actionability	Provides concrete, copy-paste-ready JSON structures for ADF, exact wiki markup syntax, and complete Confluence storage XHTML examples. The format selection criteria are specific and tied to exact field names and endpoints. The field wrappers show exactly how to embed content in API payloads.	3 / 3
Workflow Clarity	The 'Pick Format' section provides a clear decision tree for format selection, and the rules are well-sequenced. However, there are no explicit validation steps—for instance, no guidance on validating ADF JSON structure before submission, or checking that storage XHTML is well-formed. Given that malformed ADF or XHTML can cause API errors, a validation checkpoint would be valuable.	2 / 3
Progressive Disclosure	For a skill of this size and scope, the content is well-organized into clear sections (Pick Format, Rules, ADF, Wiki, Confluence Storage) that serve as a concise reference. No bundle files are needed, and the structure allows quick navigation to the relevant format without unnecessary nesting.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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: freneticdisc/grammaire
Commit: 1ce64c0

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.