ClawHub

Jira Cloud Admin

v1.0.1

Jira Cloud admin playbook. Use for Jira Cloud administration tasks: projects (company-managed/team-managed), permissions, workflows, fields/screens, automation, JSM setup (queues/SLAs/portals), reporting/dashboards, and Confluence integrations. Includes official Atlassian references and best-practice checklists in ES/EN.

⭐ 1· 952·2 current·2 all-time
by@nerdcuba
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Jira Cloud admin) match the provided materials: SKILL.md and the reference/checklist files are all Jira/Confluence administration guidance. There are no unrelated requirements (no binaries, no cloud credentials) that would be inconsistent with the stated purpose.
✓
Instruction Scope
SKILL.md contains only procedural guidance (identify project type, choose module checklist, consult Atlassian docs) and points to local reference files. It does not instruct the agent to read unrelated system files, transmit data to external endpoints other than official Atlassian docs, or perform privileged operations.
✓
Install Mechanism
No install spec and no code files (instruction-only). Nothing is downloaded or written to disk by the skill itself, so there is low installation risk.
✓
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That aligns with a documentation/playbook skill — it does not request or need secrets.
✓
Persistence & Privilege
always is false (default) and the skill does not request persistent presence or modify other skills or system settings. Autonomous invocation is enabled by default but is normal and not combined with other red flags here.
Assessment
This skill is a documentation/playbook with checklists and official Atlassian links and does not request credentials or install code — generally safe to use. Still avoid pasting any real admin credentials or exportable secrets into chats, and if you plan to follow any suggested automation actions in your environment, review them manually and test in a sandbox project first. If you need stronger assurance, confirm the author/trustworthiness before relying on it for high-risk admin changes.

Like a lobster shell, security has layers — review code before you run it.

latestvk97473m7cxypg1jtqbatx8jv9h80vkxs

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments