Add community skills, agents, system prompts from 22+ sources

Community Skills (32):
- jat: jat-start, jat-verify, jat-complete
- pi-mono: codex-cli, codex-5.3-prompting, interactive-shell
- picoclaw: github, weather, tmux, summarize, skill-creator
- dyad: 18 skills (swarm-to-plan, multi-pr-review, fix-issue, lint, etc.)
- dexter: dcf valuation skill

Agents (23):
- pi-mono subagents: scout, planner, reviewer, worker
- toad: 19 agent configs (Claude, Codex, Gemini, Copilot, OpenCode, etc.)

System Prompts (91):
- Anthropic: 15 Claude prompts (opus-4.6, code, cowork, etc.)
- OpenAI: 49 GPT prompts (gpt-5 series, o3, o4-mini, tools)
- Google: 13 Gemini prompts (2.5-pro, 3-pro, workspace, cli)
- xAI: 5 Grok prompts
- Other: 9 misc prompts (Notion, Raycast, Warp, Kagi, etc.)

Hooks (9):
- JAT hooks for session management, signal tracking, activity logging

Prompts (6):
- pi-mono templates for PR review, issue analysis, changelog audit

Sources analyzed: jat, ralph-desktop, toad, pi-mono, cmux, pi-interactive-shell,
craft-agents-oss, dexter, picoclaw, dyad, system_prompts_leaks, Prometheus,
zed, clawdbot, OS-Copilot, and more

skills/community/dyad/session-debug/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: dyad:session-debug
+description: Analyze session debugging data to identify errors and issues that may have caused a user-reported problem.
+---
+
+# Session Debug
+
+Analyze session debugging data to identify errors and issues that may have caused a user-reported problem.
+
+## Arguments
+
+- `$ARGUMENTS`: Two space-separated arguments expected:
+  1. URL to a JSON file containing session debugging data (starts with `http://` or `https://`)
+  2. GitHub issue number or URL
+
+## Instructions
+
+1. **Parse and validate the arguments:**
+
+   Split `$ARGUMENTS` on whitespace to get exactly two arguments:
+   - First argument: session data URL (must start with `http://` or `https://`)
+   - Second argument: GitHub issue identifier (number like `123` or full URL like `https://github.com/owner/repo/issues/123`)
+
+   **Validation:** If fewer than two arguments are provided, inform the user:
+
+   > "Usage: /dyad:session-debug <session-data-url> <issue-number-or-url>"
+   > "Example: /dyad:session-debug https://example.com/session.json 123"
+
+   Then stop execution.
+
+2. **Fetch the GitHub issue:**
+
+   ```
+   gh issue view <issue-number> --json title,body,comments,labels
+   ```
+
+   Understand:
+   - What problem the user is reporting
+   - Steps to reproduce (if provided)
+   - Expected vs actual behavior
+   - Any error messages the user mentioned
+
+3. **Fetch the session debugging data:**
+
+   Use `WebFetch` to retrieve the JSON session data from the provided URL.
+
+4. **Analyze the session data:**
+
+   Look for suspicious entries including:
+   - **Errors**: Any error messages, stack traces, or exception logs
+   - **Warnings**: Warning-level log entries that may indicate problems
+   - **Failed requests**: HTTP errors, timeout failures, connection issues
+   - **Unexpected states**: Null values where data was expected, empty responses
+   - **Timing anomalies**: Unusually long operations, timeouts
+   - **User actions before failure**: What the user did leading up to the issue
+
+5. **Correlate with the reported issue:**
+
+   For each suspicious entry found, assess:
+   - Does the timing match when the user reported the issue occurring?
+   - Does the error message relate to the feature/area the user mentioned?
+   - Could this error cause the symptoms the user described?
+
+6. **Rank the findings:**
+
+   Create a ranked list of potential causes, ordered by likelihood:
+
+   ```
+   ## Most Likely Causes
+
+   ### 1. [Error/Issue Name]
+   - **Evidence**: What was found in the session data
+   - **Timestamp**: When it occurred
+   - **Correlation**: How it relates to the reported issue
+   - **Confidence**: High/Medium/Low
+
+   ### 2. [Error/Issue Name]
+   ...
+   ```
+
+7. **Provide recommendations:**
+
+   For each high-confidence finding, suggest:
+   - Where in the codebase to investigate
+   - Potential root causes
+   - Suggested fixes if apparent
+
+8. **Summarize:**
+   - Total errors/warnings found
+   - Top 3 most likely causes
+   - Recommended next steps for investigation