Detailed changes
@@ -30,6 +30,12 @@ agent capabilities through a standardised format.
- [resolving-secrets](skills/resolving-secrets/SKILL.md): Wraps shell
commands to resolve secret references in environment variables. Use
when invoking `synu`, `crush`, `gh`, `hut`, etc.
+- [deferring-work-through-lunatask](skills/deferring-work-through-lunatask/SKILL.md):
+ Captures findings, suggestions, and deferred work items in Lunatask
+ with rich context for future sessions.
+- [resuming-work-through-lunatask](skills/resuming-work-through-lunatask/SKILL.md):
+ Resumes previously deferred work from Lunatask. Use when user pastes a
+ task note, shares a deep link, or references continuing earlier work.
## Installation
@@ -0,0 +1,78 @@
+---
+name: deferring-work-through-lunatask
+description: Captures findings, suggestions, and deferred work items in Lunatask with rich context for future sessions. Use when user says "we'll tackle this later", when you suggest improvements the user wants to defer, or when identifying issues to address separately.
+compatibility: Requires Lunatask MCP tools or CLI access
+license: AGPL-3.0-or-later
+metadata:
+ author: Amolith <amolith@secluded.site>
+---
+
+## Formatting
+
+### Title
+
+Titles must be:
+
+- Useful and concise
+- Conversational
+- Include the project name
+
+Example: `Implement FunctionSignature(Args) in go-lunatask`
+
+### Status
+
+New tasks usually get status `later`.
+
+### Note structure
+
+Use `[Title](lunatask://...)` syntax if deep links are needed.
+
+```markdown
+> [Warm, direct message to user—make them smile when they find this later]
+
+---
+
+Hello, future me! o/
+
+[Thorough description of the work: what needs doing, why it matters, relevant context discovered during the session]
+
+[Follow our slow and methodical planning approach: read relevant source code, documentation, and APIs before acting]
+
+When starting this task, update status according to workflow. When finished, mark `complete`.
+
+ID: PLACEHOLDER_ID
+```
+
+After creation, update the note to replace `PLACEHOLDER_ID` with the actual task ID from the creation response.
+
+### References trailer
+
+When user references external resources (issues, commits, PRs, tickets), append a `References:` section:
+
+```markdown
+References:
+
+- https://github.com/user/repo/issues/123
+- project-name/commit/abc123
+- project-name/todo/456
+```
+
+Prefer web links; fall back to `project-name/type/id` format.
+
+## Appending to existing notes
+
+Only append—never overwrite unless explicitly asked.
+
+Lunatask only supports full replacement, so reproduce the original note verbatim, then add:
+
+```markdown
+---
+
+[New content here]
+```
+
+Use well-formed markdown with proper whitespace between sections.
+
+## CLI fallback
+
+If `lunatask` or `lune` MCP tools are unavailable, see [cli.md](references/cli.md).
@@ -0,0 +1,38 @@
+# CLI Reference
+
+When MCP tools are unavailable, use `lune` CLI.
+
+## Creating tasks
+
+```bash
+lune task add "Title" -a AREA_KEY -n "$(cat <<'EOF'
+Note content
+EOF
+)"
+```
+
+<task_add_flags>
+-a --area Area key (required)
+-s --status Status (workflow-dependent)
+-n --note Task note (use - for stdin)
+-g --goal Goal key
+</task_add_flags>
+
+Output includes the task ID needed to replace `PLACEHOLDER_ID` in the note.
+
+## Updating notes
+
+```bash
+lune task update ID -n "$(cat <<'EOF'
+Full replacement content
+EOF
+)"
+```
+
+Notes are replaced entirely—reproduce original content when appending.
+
+## Listing areas
+
+```bash
+lune area list
+```
@@ -0,0 +1 @@
+Read through https://git.secluded.site/lune/blob/main/README.md?raw=1 and help the user through installing/setting up either lune's CLI or MCP. The CLI with this skill would be more efficient for e.g. coding agents, but the MCP server is required for integrating with something like Home Assistant.
@@ -0,0 +1,21 @@
+---
+name: resuming-work-through-lunatask
+description: Resumes previously deferred work from Lunatask. Use when user pastes a task note, shares a lunatask:// deep link, says "let's pick this up", or references continuing earlier work.
+compatibility: Requires Lunatask MCP tools or CLI access
+license: AGPL-3.0-or-later
+metadata:
+ author: Amolith <amolith@secluded.site>
+---
+
+Treat the provided plan as **high-level suggestions only**. Before acting:
+
+1. Read relevant source code, documentation, and library APIs
+2. Verify the plan is still accurate, necessary, and beneficial
+3. If deviations exist between the plan and current state:
+ - Stop
+ - Summarize the deviations
+ - Wait for user input before proceeding
+
+## CLI fallback
+
+If `lunatask` or `lune` MCP tools are unavailable, see [cli.md](references/cli.md).
@@ -0,0 +1,25 @@
+# CLI Reference
+
+When MCP tools are unavailable, use `lune` CLI.
+
+## Showing task details
+
+```bash
+lune task show ID
+```
+
+Accepts UUID or `lunatask://` deep link. Due to encryption, name/note aren't visible—only metadata.
+
+## Updating status
+
+```bash
+lune task update ID -s STATUS
+```
+
+Valid statuses depend on the area's workflow (see `lune area list`).
+
+## Marking complete
+
+```bash
+lune done ID
+```
@@ -0,0 +1 @@
+Read through https://git.secluded.site/lune/blob/main/README.md?raw=1 and help the user through installing/setting up either lune's CLI or MCP. The CLI with this skill would be more efficient for e.g. coding agents, but the MCP server is required for integrating with something like Home Assistant.