@troykelly/openclaw-projects 0.0.35 → 0.0.37

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@troykelly/openclaw-projects",
-  "version": "0.0.35",
+  "version": "0.0.37",
   "description": "OpenClaw memory plugin with projects, todos, and contacts integration",
   "type": "module",
   "main": "dist/index.js",

package/skills/api-integration/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: api-integration
+description: Onboard a new external API, configure credentials, and verify endpoints
+args:
+  - name: name
+    description: Name or identifier for the API to integrate
+    required: true
+---
+
+Onboard the external API "{{name}}" and verify it is searchable:
+
+1. **Onboard the API**
+   - Use `api_onboard` to register the new API source
+   - Provide the API name "{{name}}" and any base URL or documentation URL the user supplies
+   - Capture the returned source ID for subsequent steps
+
+2. **Configure Credentials**
+   - Use `api_credential_manage` to set up authentication for the API
+   - Ask the user what auth method the API requires (API key, OAuth, bearer token, etc.)
+   - Store the credentials securely against the onboarded source
+
+3. **Verify Discoverability**
+   - Use `api_recall` to search for the newly onboarded API by name
+   - Confirm the API appears in search results with correct metadata
+   - If not found, check the onboarding details and retry
+
+4. **Refresh and Confirm**
+   - Use `api_refresh` to ensure the API index is up to date
+   - Use `api_recall` again to confirm the API and its endpoints are fully indexed
+   - Report the final status and available endpoints to the user
+
+## Important Notes:
+- Never log or display raw API keys or tokens
+- If the API requires OAuth, guide the user through the flow
+- Suggest testing a sample endpoint after setup is complete

package/skills/contact-relationship-map/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: contact-relationship-map
+description: Build a comprehensive view of a contact with relationships, links, and memories
+args:
+  - name: name
+    description: Contact name to map
+    required: true
+---
+
+Build a comprehensive relationship map for contact "{{name}}":
+
+1. **Retrieve Contact Details**
+   - Use `contact_search` to find the contact by name "{{name}}"
+   - Use `contact_get` with the contact ID to retrieve full details
+   - Show all known endpoints (email, phone, social accounts)
+   - If multiple matches found, ask for clarification
+
+2. **Map Relationships**
+   - Use `relationship_query` with the contact ID to find all relationships
+   - Show each related contact and the relationship type (colleague, family, manager, etc.)
+   - Note the direction of each relationship (e.g., "reports to" vs "manages")
+
+3. **Find Linked Items**
+   - Use `links_query` with the contact's entity reference to discover linked content
+   - Show linked projects, tasks, notes, and other work items
+   - Highlight any active or high-priority linked items
+
+4. **Recall Stored Memories**
+   - Use `memory_recall` with the contact's name to find relevant memories
+   - Show preferences, facts, past decisions, and contextual notes
+   - Note when each memory was stored for recency context
+
+5. **Relationship Map Summary**
+   - Present a unified view:
+     - Contact card (name, endpoints, notes)
+     - Relationship network (connected people and relationship types)
+     - Linked work (projects, tasks, notes referencing this contact)
+     - Stored context (memories and preferences)
+   - Suggest any missing information worth capturing

package/skills/dev-session-report/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: dev-session-report
+description: Generate a summary report for a completed dev session
+args:
+  - name: session_id
+    description: Dev session UUID (use dev_session_list to find sessions)
+    required: true
+---
+
+Generate a summary report for dev session "{{session_id}}":
+
+1. **Retrieve Session Details**
+   - If the user provided a name instead of a UUID, use `dev_session_list` to find matching sessions first
+   - Use `dev_session_get` with the session UUID "{{session_id}}"
+   - Show session name, start time, duration, and current status
+   - If the session is still active, ask whether to complete it first
+
+2. **Complete Session (if needed)**
+   - If the session is still in progress, use `dev_session_complete` to close it
+   - Ask the user for a summary of what was accomplished
+   - Record any final notes or outcomes
+
+3. **Gather Related Work Items**
+   - Use `todo_list` to find tasks linked to this dev session
+   - Categorize tasks by status (completed during session, still pending, blocked)
+   - Calculate completion metrics (tasks done vs remaining)
+
+4. **Add Project Context**
+   - Use `project_get` to retrieve the parent project details
+   - Show how the session's work fits into overall project progress
+   - Note any milestones reached or approaching
+
+5. **Compile Report**
+   - Present a structured report with:
+     - Session overview (duration, focus area)
+     - Accomplishments (completed tasks, key decisions)
+     - Remaining work (pending tasks, blockers)
+     - Project impact (progress toward goals)
+   - Suggest storing the report as a memory for future reference

package/skills/namespace-audit/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: namespace-audit
+description: Audit namespace content by searching across projects, memories, and items
+args:
+  - name: namespace
+    description: Namespace to audit (optional, audits current namespace if omitted)
+    required: false
+---
+
+Audit the namespace "{{namespace}}" to review its content and usage:
+
+1. **Search Namespace Content**
+   - Use `context_search` with a broad query to discover items in the namespace
+   - Note the types of content found (memories, projects, tasks, notes)
+   - Report the total number of items discovered
+
+2. **Review Projects**
+   - Use `project_list` to find all projects in the namespace scope
+   - For each project, note its status, task count, and last activity
+   - Identify any stale or abandoned projects
+
+3. **Check Stored Memories**
+   - Use `memory_recall` with a general query to find memories in the namespace
+   - Categorize memories by type (preference, fact, decision, context)
+   - Flag any outdated or potentially stale memories
+
+4. **Audit Summary**
+   - Present a comprehensive namespace overview:
+     - Total items by type (projects, tasks, memories, notes)
+     - Active vs stale content
+     - Storage utilization patterns
+   - Recommend cleanup actions for stale or orphaned content
+   - Suggest namespace organization improvements
+
+## Important Notes:
+- If no namespace is specified, the audit runs against the current default namespace
+- Large namespaces may require multiple queries; paginate as needed
+- Do not delete any content during the audit; only recommend actions

package/skills/note-meeting/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: note-meeting
+description: Create meeting notes with attendees, action items, and linked references
+args:
+  - name: title
+    description: Meeting title or topic
+    required: true
+---
+
+Create comprehensive meeting notes for "{{title}}":
+
+1. **Create the Meeting Note**
+   - Use `notebook_list` to find or select the appropriate notebook for meeting notes
+   - Use `note_create` to create a new note titled "{{title}}"
+   - Include the date, time, and meeting topic in the note body
+   - Ask the user for the key discussion points and decisions
+
+2. **Identify Attendees**
+   - Use `contact_search` to look up each attendee mentioned by the user
+   - For each found contact, note their name and role
+   - If an attendee is not in contacts, offer to create them with `contact_create`
+
+3. **Extract Action Items**
+   - For each action item identified during the meeting:
+     - Use `todo_create` to create a task with a clear title (include assignee name in the title if known)
+     - Set the due date if provided
+     - Prefix the title with the responsible person's name for easy filtering
+
+4. **Link Everything Together**
+   - Use `links_set` to link the meeting note to:
+     - Each attendee's contact record
+     - Each action item created
+     - Any referenced projects or existing work items
+   - This creates a navigable web of meeting context
+
+5. **Summary**
+   - Present the completed meeting note with:
+     - Attendee list with contact links
+     - Numbered action items with owners and due dates
+     - Links to related projects or work items
+   - Confirm all items are correctly captured
+
+## Important Notes:
+- Ask for clarification on ambiguous action items before creating todos
+- If attendees have multiple matching contacts, ask the user to confirm
+- Suggest a follow-up reminder if a next meeting date is mentioned

package/skills/terminal-setup/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: terminal-setup
+description: Set up a new terminal connection with credentials and verification
+args:
+  - name: host
+    description: Hostname or IP address of the remote server
+    required: true
+  - name: label
+    description: Friendly name for this connection
+    required: false
+---
+
+Set up a new terminal connection to "{{host}}" and verify it works:
+
+1. **Create Credentials First**
+   - Ask the user for their preferred auth method (password, SSH key, or key file)
+   - Use `terminal_credential_create` to store the credential securely
+   - Note the returned credential ID for the next step
+
+2. **Create the Connection**
+   - Use `terminal_connection_create` with the host "{{host}}" and the `credential_id` from step 1
+   - Set the name to "{{label}}" if provided, otherwise use the hostname
+   - Configure the connection type (SSH is the default)
+
+3. **Test the Connection**
+   - Use `terminal_connection_test` with the connection ID to verify it works
+   - If the test fails, report the error details clearly
+   - Suggest common fixes (wrong port, firewall, credential issues)
+
+4. **Confirm Setup**
+   - Use `terminal_connection_list` to show the new connection in the list
+   - Report the connection ID for future reference
+   - Suggest next steps (starting a session, creating a tunnel)
+
+## Important Notes:
+- Never store or log raw passwords or private keys
+- If SSH key auth is chosen, the key content should be provided securely
+- Default SSH port is 22; ask if a non-standard port is needed

package/skills/weekly-review/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: weekly-review
+description: Comprehensive weekly review of projects, tasks, communications, and sessions
+---
+
+Perform a comprehensive weekly review covering all key areas:
+
+1. **Project Progress**
+   - Use `project_list` to get all active projects
+   - For each project, summarize current status and recent changes
+   - Highlight projects with approaching deadlines or at-risk milestones
+
+2. **Task Review**
+   - Use `todo_search` to find tasks completed this week
+   - Use `todo_search` to find tasks that are overdue or due soon
+   - Calculate completion rate and identify any bottlenecks
+   - List the top priority pending tasks for the coming week
+
+3. **Communications Summary**
+   - Use `message_search` to find messages from the past week
+   - Summarize key conversations and any unanswered messages
+   - Note any threads requiring follow-up
+
+4. **Dev Sessions**
+   - Use `dev_session_list` to find sessions from the past week
+   - Summarize what was worked on and key outcomes
+   - Note any sessions that were started but not completed
+
+5. **Notes and Documentation**
+   - Use `note_search` to find notes created or updated this week
+   - Highlight meeting notes, decisions, and important captures
+   - Flag any notes that need follow-up action
+
+6. **Weekly Summary**
+   - Present a structured review:
+     - Wins: completed tasks, shipped features, resolved issues
+     - In Progress: ongoing work and expected completion
+     - Blockers: items needing attention or escalation
+     - Upcoming: priorities and deadlines for next week
+   - Suggest focus areas for the coming week based on priorities and deadlines