action-item-organizer
Organize Action Items from Documents
Important follow-ups are easy to miss in long notes, reports, and audits. This skill extracts tasks, priorities, owners, locations, and estimates into trackable markdown checklists.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "action-item-organizer" from https://skillstore.io/skills/89jobrien-action-item-organizer.md and its manifest at https://skillstore.io/api/skills/89jobrien-action-item-organizer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "action-item-organizer". A code review report lists missing authentication, hardcoded credentials, and several performance improvements.
Expected outcome:
- A P0 section lists security blockers with owners, estimates, and source files.
- A P1 section captures performance work with the reason and expected impact.
- A completion summary shows total items and estimated effort.
Using "action-item-organizer". Meeting notes mention documentation updates, deployment fixes, and future design ideas.
Expected outcome:
- Urgent deployment work is placed before launch-related documentation tasks.
- Future ideas are grouped as lower priority items for later planning.
- Named owners are preserved and missing estimates are marked for review.
Using "action-item-organizer". An audit report contains findings across security, reliability, testing, and documentation.
Expected outcome:
- Findings become grouped checklist sections by priority and category.
- Each task keeps its rationale so teams understand the remediation goal.
- Nested steps break complex fixes into smaller trackable actions.
Security Audit
SafeAll static findings were adjudicated as false positives. The flagged shell execution, secret, system, and network reconnaissance patterns appear only in markdown examples, inline file-path formatting, or priority guidance. No prompt injection text or malicious intent was found in the reviewed cited files.
Risk Factors
⚙️ External commands (30)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/89jobrien-action-item-organizer/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/89jobrien-action-item-organizer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/89jobrien-action-item-organizer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/89jobrien-action-item-organizer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/89jobrien-action-item-organizer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Joseph OBrien. (2026). action-item-organizer security audit report (audit version 6) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/89jobrien-action-item-organizer/audits/6BibTeX citation
@techreport{joseph-obrien-89jobrien-action-item-organizer-2026,
author = {Joseph OBrien},
title = {action-item-organizer security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/89jobrien-action-item-organizer/audits/6},
note = {Author version 1.0.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "action-item-organizer security audit report (audit version 6)"
version: "1.0.1"
type: report
authors:
- name: "Joseph OBrien"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/89jobrien-action-item-organizer/audits/6"
identifiers:
- type: other
value: "skillstore:89jobrien-action-item-organizer:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Convert Meeting Notes
Turn scattered follow-ups into clear owners, priorities, and next steps after a planning meeting.
Organize Review Findings
Convert code review or design review comments into prioritized remediation tasks with source locations.
Track Audit Remediation
Group audit findings by severity and produce a checklist that teams can execute and monitor.
Try These Prompts
Use the action-item-organizer skill to extract every action item from this document. Group the results by priority and include owners when named.
Extract action items from this report. Preserve file paths, line numbers, owners, estimates, tracking IDs, and the original reason for each task.
Organize these notes into P0 through P3 sections. Explain the priority choice in the context field when the source is ambiguous.
Combine these documents into one deduplicated action item checklist. Preserve source references and nest dependent tasks under the main deliverable.
Best Practices
- Provide the full source document so the skill can preserve context and dependencies.
- Review inferred priorities when the source does not provide severity or urgency.
- Keep source references in the checklist so teams can trace each task back to evidence.
Avoid
- Do not ask for a checklist from partial notes when missing sections contain action items.
- Do not remove source context from high-risk tasks or audit findings.
- Do not treat inferred owners, estimates, or priorities as final without review.
Frequently Asked Questions
What document types can this skill process?
Does it create tickets in external tools?
How does it decide priority?
Can it keep file paths and line numbers?
What happens when metadata is missing?
Is human review still needed?
Developer Details
Author
Joseph OBrienLicense
MIT
Author version
v1.0.1
Skillstore revision
r1
Ref
c4037264bbd363c572662d6154a3ab28f5ca4f53
Maintenance freshness
7/18/2026
Usage
11 downloads · 315 views
File structure