rh-ssg-legal-and-support
Skill4 starsChanged 4 months agoApache-2.0View on GitHub
Review Red Hat documentation for SSG legal and support compliance — no cost/pricing references, no future release promises, Developer Preview requirements and Technology Preview requirements. Use this skill when checking Red Hat docs for Technology Preview, Developer Preview, TP/DP admonitions, cost language, future release statements, or support scope compliance. Takes precedence over ibm-sg-legal-information for Red Hat content.
In this repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- action-commentsSkill
- article-extractorSkill
- docs-convert-gdoc-mdSkill
- docs-orchestratorSkill
- docs-review-content-qualitySkill
- docs-review-modular-docsSkill
- docs-review-securitySkill
- docs-review-styleSkill
- docs-review-technicalSkill
- docs-ticket-readinessSkill
- docs-workflow-code-analysisSkill
- docs-workflow-create-jiraSkill
- docs-workflow-create-merge-requestSkill
- docs-workflow-jira-readySkill
- docs-workflow-pipeline-diagnosticsSkill
- docs-workflow-planningSkill
- docs-workflow-pr-analysisSkill
- docs-workflow-quality-gateSkill
- docs-workflow-requirementsSkill
- docs-workflow-scope-req-auditSkill
- docs-workflow-security-reviewSkill
- docs-workflow-startSkill
- docs-workflow-style-reviewSkill
- docs-workflow-tech-reviewSkill
- docs-workflow-writingSkill
- git-pr-readerSkill
- ibm-sg-audience-and-mediumSkill
- ibm-sg-language-and-grammarSkill
- ibm-sg-legal-informationSkill
- ibm-sg-numbers-and-measurementSkill
- ibm-sg-punctuationSkill
- ibm-sg-referencesSkill
- ibm-sg-structure-and-formatSkill
- ibm-sg-technical-elementsSkill
- jira-readerSkill
- jira-writerSkill
- learn-codeSkill
- lint-with-valeSkill
- mdita-writeSkill
- query-codeSkill
- redhat-docs-tocSkill
- rh-ssg-accessibilitySkill
- rh-ssg-formattingSkill
- rh-ssg-grammar-and-languageSkill
- rh-ssg-gui-and-linksSkill
- rh-ssg-release-notesSkill
- rh-ssg-structureSkill
- rh-ssg-technical-examplesSkill
- rn-known-issuesSkill
- understand-pull-requestSkill
- validate-plugin-prereqsSkill
The file
Files
Red Hat SSG: Legal and Support review skill
Review documentation for legal and support compliance with the Red Hat Supplementary Style Guide.
Checklist
Cost references
- No references to costs or charges of Red Hat products
- No use of "free," "at no initial cost," or similar cost language
- Cost information is left to marketing materials
Future releases or plans
- No promises that a feature or fix will be included in a specific future release
- No references to specific future release numbers or dates
- Future plans use words like "anticipate," "expect," or "plan"
- Exception: deprecation/removal notices may specify a future release
Developer Preview
- "Developer Preview" uses initial uppercase capitalization
- IMPORTANT admonition with required template text is included at the beginning of Developer Preview content
- The phrase "supported as a Developer Preview" is never used
- The word "support" is avoided in Developer Preview descriptions — use "available," "provide," "capability" instead
- When feature becomes GA, the IMPORTANT admonition is removed
Technology Preview
- "Technology Preview" uses initial uppercase capitalization — never "Tech Preview" or "Technical Preview"
- IMPORTANT admonition with required template text is included at the beginning of Technology Preview content
- The phrase "supported as a Technology Preview" is never used
- The word "support" is avoided — use "available," "provide," "capability," "functionality," "enable" instead
- For hardware: "recognize" is the correct term (components recognize devices)
- When feature becomes GA, the IMPORTANT admonition is removed
- Brief description is included in the release notes
How to use
- Review only changed content and necessary context
- For each issue found, cite the relevant SSG section
- Mark issues as required (missing TP/DP admonitions, cost references, future release promises) or [SUGGESTION] (wording improvements)
Example invocations
- "Review this file for legal and support compliance"
- "Check Technology Preview and Developer Preview admonitions"
- "Do an SSG legal review on the release notes"
References
For detailed guidance, consult:
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

