jira-write-ticket
Use when asked to write a Jira ticket.
[](https://agentverus.ai/skill/b76b44b4-1252-4a02-a410-6b0b38378eef)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/b76b44b4-1252-4a02-a410-6b0b38378eef/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"b76b44b4-1252-4a02-a410-6b0b38378eef","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/b76b44b4-1252-4a02-a410-6b0b38378eef/trustCategory Scores
Findings (3)
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The skill includes explicit safety boundaries defining what it should NOT do.
→ Keep these safety boundaries. They improve trust.
The skill includes output format constraints (length limits, format specifications).
→ Keep these output constraints.