Add a comment to a case to document findings, actions, or recommendations. Use to maintain audit trail during investigations. Requires CASE_ID and comment text.
Install with Tessl CLI
npx tessl i github:dandye/ai-runbooks --skill document-in-case81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Add a standardized comment to a case to document findings, actions taken, or recommendations.
CASE_ID - The SOAR case ID to add the comment toCOMMENT_TEXT - The full text of the comment to be addedALERT_GROUP_IDENTIFIERS - Alert group identifiers if requiredsecops-soar.post_case_comment(
case_id=CASE_ID,
comment=COMMENT_TEXT,
alert_group_identifiers=ALERT_GROUP_IDENTIFIERS // if provided
)Check the API response to confirm the comment was posted successfully.
| Output | Description |
|---|---|
COMMENT_POST_STATUS | Success/failure status of the comment posting |
Enrichment Summary:
IOC Enrichment for [IOC_VALUE] ([IOC_TYPE]):
- GTI Reputation: [score/classification]
- SIEM Activity: [first/last seen, alert count]
- IOC Match: [Yes/No]
- Assessment: [Low/Medium/High risk]
- Recommendation: [next steps]Triage Decision:
Alert Triage Complete:
- Classification: [FP/BTP/TP/Suspicious]
- Key Findings: [summary]
- Rationale: [why this classification]
- Action Taken: [closed/escalated]Investigation Update:
Investigation Update [timestamp]:
- Actions Completed: [list]
- Findings: [summary]
- Next Steps: [planned actions]67a00be
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.