Install
$ agentstack add skill-igptai-skills-decision-log ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Decision Log
Prerequisites
This skill needs the iGPT MCP at https://mcp.igpt.ai/.
If the MCP tools aren't available or return an auth error, tell the user to install the iGPT plugin (/plugin marketplace add igptai/skills) or add https://mcp.igpt.ai/ as a connector, then complete OAuth and say "ready". Retry once after they confirm. Never invent tokens or OAuth URLs. For deeper troubleshooting: https://raw.githubusercontent.com/igptai/skills/main/shared/mcp-guard.md
What This Skill Does
Traces all significant decisions made in project email threads and assembles them into a chronological decision log — what was decided, by whom, when, what alternatives were considered, and any conditions or caveats attached.
Workflow
- Before calling any tool, collect these values from the user. Offer the
defaults and let the user override them; do not invent values they did not give.
- [time_range] — what window of email to scan. The user may give this
in any form ("last 90 days", "the last 3 months", "May 2024", "since the kickoff"). Default: the last 90 days. Keep the user's natural phrasing for use in the ask input; convert to ISO dates separately for the search call.
- [project_scope] — either "all" (default) or the name or topic of a
specific project to focus on.
- [projectclause] — derived. When [projectscope] is not "all", set
to " related to [projectscope]". When [projectscope] is "all", set to empty string.
- Call search with:
- query: decided agreed going with chosen approved decided on
(if [project_scope] is not "all", append the project name to the query)
- datefrom: ISO start date derived from [timerange]
- dateto: ISO end date derived from [timerange] (or today if open-ended)
- Call ask with:
- input: Review all email threads from [timerange][projectclause]. Identify every significant decision that was made — explicit choices, direction changes, scope decisions, technical choices, vendor selections, and any other point where a clear direction was established. For each decision record: what was decided, who made the decision, when, what alternatives were considered if mentioned, and any conditions or caveats attached to the decision.
- output_format:
{ "strict": true, "schema": { "type": "object", "description": "Chronological decision log for a project extracted from email history", "additionalProperties": false, "properties": { "project": { "type": "string", "description": "Name or description of the project" }, "periodfrom": { "type": "string", "description": "ISO8601 start date of the period covered" }, "periodto": { "type": "string", "description": "ISO8601 end date of the period covered" }, "decisions": { "type": "array", "description": "Chronological list of every significant decision found in email", "items": { "type": "object", "description": "A single project decision with full context", "additionalProperties": false, "properties": { "decision": { "type": "string", "description": "Clear statement of what was decided" }, "decisiontype": { "type": "string", "description": "Category of decision", "enum": [ "scope", "technical", "vendorselection", "timeline", "budget", "resource", "process", "directionchange", "other" ] }, "decidedby": { "type": "string", "description": "Name or role of the person who made or ratified this decision" }, "date": { "type": "string", "description": "ISO8601 date the decision was made" }, "alternativesconsidered": { "type": "array", "description": "Other options that were discussed before this decision was made", "items": { "type": "string", "description": "A single alternative that was considered" } }, "rationale": { "type": "string", "description": "The reason given for this decision if stated in email, empty string if not mentioned" }, "conditionsorcaveats": { "type": "string", "description": "Any conditions, assumptions, or caveats attached to this decision, empty string if none" }, "evidence": { "type": "string", "description": "Quote or paraphrase from email that documents this decision" } }, "required": [ "decision", "decisiontype", "decidedby", "date", "alternativesconsidered", "rationale", "conditionsorcaveats", "evidence" ] } }, "totaldecisions": { "type": "number", "description": "Total number of decisions logged" }, "summary": { "type": "string", "description": "One or two sentence summary of the decision history and any notable patterns" } }, "required": [ "project", "periodfrom", "periodto", "decisions", "totaldecisions", "summary" ] } }
- Present as a numbered chronological log. Lead with total count and a
one-line summary of the decision landscape.
- Ask: "Would you like me to export this as a formatted decision log
document?"
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: igptai
- Source: igptai/skills
- License: MIT
- Homepage: https://www.igpt.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.