Publish Jira
v1.0.0Full-featured Atlassian Jira Cloud REST API v3 skill. Manage issues, sprints, boards, epics, projects, users, and more via direct Jira API calls. Use when ma...
⭐ 0· 19·0 current·0 all-time
byAlienTree@jeffersonling1217-png
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe a Jira Cloud REST API integration and the required environment variables (JIRA_EMAIL, JIRA_API_TOKEN, JIRA_DOMAIN) directly match that purpose; no unrelated services, binaries, or config paths are requested.
Instruction Scope
SKILL.md contains API endpoint usage, sample requests, and auth instructions limited to Jira REST endpoints. It does not instruct reading unrelated files, scanning system state, or sending data to external endpoints outside the Jira domain templates.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk or downloaded during install, which is low-risk and appropriate for a documentation-driven integration.
Credentials
Only three env vars are required (email, API token, domain), all necessary for Basic Auth against Jira Cloud. The API token is sensitive but its presence is justified by the described functionality.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent system-level privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill appears coherent, but be cautious before providing real credentials: use a dedicated Jira API token with least privilege (or a service account) and point it at a test project first. Verify the skill’s source/homepage and consider rotating the token after testing. Because the agent will make API calls using your token, audit your Jira access logs and limit network exposure if possible. If you need stronger assurance, request the skill author’s provenance or use an intermediary proxy that logs outbound calls for inspection.Like a lobster shell, security has layers — review code before you run it.
latestvk978r4hht47wb1exsx5v1p964d84eg87
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
✅ Clawdis
EnvJIRA_EMAIL, JIRA_API_TOKEN, JIRA_DOMAIN