Define requirements for an OpenClaw integration
Document a proposed integration's data needs, actions, credentials, and review boundaries.
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
--- version: 4.1.0-fractal name: team-collaboration-standup-notes-afa020447381 description: "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns." --- # Standup Notes Generator You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns. ## Use this skill when - Working on standup notes generator tasks or workflows - Needing guidance, best practices, or checklists for standup notes generator ## Do not use this skill when - The task is unrelated to standup notes generator - You need a different domain or tool outside this scope ## Context Modern remote-first teams rely on async standup notes to maintain visibility, coordinate work, and identify blockers without synchronous meetings. This tool generates comprehensive daily standup notes by analyzing multiple data sources: Obsidian vault context, Jira tickets, Git commit history, and calendar events. It supports both traditional synchronous standups and async-first team communication patterns, automatically extracting accomplishments from commits and formatting them for maximum team visibility. ## Requirements **Arguments:** `$ARGUMENTS` (optional) - If provided: Use as context about specific work areas, projects, or tickets to highlight - If empty: Automatically discover work from all available sources **Required MCP Integrations:** - `mcp-obsidian`: Vault access for daily notes and project updates - `atlassian`: Jira ticket queries (graceful fallback if unavailable) - Optional: Calendar integrations for meeting context ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples. ## 🧠 Knowledge Modules (Fractal Skills) ### 1. [implementation-playbook](./sub-skills/implementation-playbook.md)--- version: 4.1.0-fractal name: team-collaboration-standup-notes-afa020447381 description: "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns." --- # Standup Notes Generator You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns. ## Use this skill when - Working on standup notes generator tasks or workflows - Needing guidance, best practices, or checklists for standup notes generator ## Do not use this skill when - The task is unrelated to standup notes generator - You need a different domain or tool outside this scope ## Context Modern remote-first teams rely on async standup notes to maintain visibility, coordinate work, and identify blockers without synchronous meetings. This tool generates comprehensive daily standup notes by analyzing multiple data sources: Obsidian vault context, Jira tickets, Git commit history, and calendar events. It supports both traditional synchronous standups and async-first team communication patterns, automatically extracting accomplishments from commits and formatting them for maximum team visibility. ## Requirements **Arguments:** `$ARGUMENTS` (optional) - If provided: Use as context about specific work areas, projects, or tickets to highlight - If empty: Automatically discover work from all available sources **Required MCP Integrations:** - `mcp-obsidian`: Vault access for daily notes and project updates - `atlassian`: Jira ticket queries (graceful fallback if unavailable) - Optional: Calendar integrations for meeting context ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples. ## 🧠 Knowledge Modules (Fractal Skills) ### 1. [implementation-playbook](./sub-skills/implementation-playbook.md)
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.