@ekkos/cli 1.3.1 → 1.3.5

package/templates/windsurf-skills/ekkos-recall/SKILL.md

@@ -1,96 +0,0 @@
----
-name: ekkos-recall
-description: Deep memory retrieval across sessions and projects. Activate when the user says "yesterday", "last week", "remember when", "what did we discuss", "we worked on X before", "bring context from", or asks about past decisions, fixes, or discussions. Combines time-based recall with semantic search.
-allowed-tools:
-  - mcp__ekkos-memory__ekkOS_Recall
-  - mcp__ekkos-memory__ekkOS_Search
-  - mcp__ekkos-memory__ekkOS_Context
-  - mcp__ekkos-memory__ekkOS_RestoreContext
----
-
-# ekkOS Deep Recall
-
-You can recall past conversations, decisions, and context from previous sessions.
-
-## When To Activate
-
-| Trigger | Example |
-|---------|---------|
-| Time reference | "yesterday", "last week", "last month" |
-| Past work | "remember when we...", "we worked on X before" |
-| Decision recall | "what did we decide about...", "why did we choose..." |
-| Context transfer | "bring context from the other project" |
-| Session continuity | "where did we leave off", "continue from last time" |
-
-## Instructions
-
-### Time-Based Recall
-
-```
-ekkOS_Recall({
-  days_ago: 1,                    // 1, 2, 7, 30...
-  semantic_query: "what we discussed about auth",
-  include_file_changes: true,     // show files modified
-  include_patterns: true,         // show patterns used
-  extract_decisions: true,        // pull out decisions made
-  group_by_sessions: true         // organize by session
-})
-```
-
-### Semantic Recall (By Topic)
-
-```
-ekkOS_Recall({
-  semantic_query: "database migration strategy",
-  limit: 10,
-  include_full_content: true
-})
-```
-
-### Session-Based Recall
-
-```
-ekkOS_Recall({
-  session_id: "<session-id>",
-  from_turn: 1,
-  to_turn: 50,
-  include_full_content: true
-})
-```
-
-### Context Restoration (After Compaction)
-
-When you see `<ekkos-context-preserved>` with a restoration token:
-
-```
-ekkOS_RestoreContext({
-  restoration_token: "<token from tag>"
-})
-```
-
-## Response Format
-
-Present recalled information clearly:
-
-```
-🧠 From [date/session]:
-
-**Topic:** [what was discussed]
-**Decision:** [what was decided]
-**Files changed:** [list]
-**Patterns used:** [list]
-**Key insight:** [the important takeaway]
-```
-
-## Integration with Golden Loop
-
-Recall is an extended SEARCH — it queries episodic memory (L2) instead of pattern memory (L4). Results should still be acknowledged and tracked like any retrieval.
-
-After recalling useful context, record the outcome:
-```
-ekkOS_Outcome({ success: true })
-```
-
----
-
-**Mantra**: Nothing is forgotten. Every session is searchable. Context persists.

package/templates/windsurf-skills/ekkos-safety/SKILL.md

@@ -1,89 +0,0 @@
----
-name: ekkos-safety
-description: Check for conflicts before dangerous operations. Activate before deleting files, dropping tables, deploying to production, pushing to main, running destructive commands, modifying configuration files, force-pushing, or any irreversible action. Prevents accidents by checking user directives and patterns.
-allowed-tools:
-  - mcp__ekkos-memory__ekkOS_Conflict
-  - mcp__ekkos-memory__ekkOS_Search
----
-
-# ekkOS Safety Guard
-
-Check for conflicts with user directives and patterns before destructive operations.
-
-## When To Activate
-
-**MUST fire before:**
-- `rm -rf`, `rm -r`, deleting files or directories
-- `DROP TABLE`, `DELETE FROM`, `TRUNCATE`
-- `git push --force`, `git reset --hard`
-- Deploying to production
-- Modifying CI/CD pipelines
-- Changing environment variables
-- Overwriting configuration files
-- Killing processes
-- Any command that is hard to reverse
-
-## Instructions
-
-### Step 1: Check for Conflicts
-
-```
-ekkOS_Conflict({
-  proposed_action: "delete all migration files in /db/migrations",
-  scope: "deployment"   // optional: deployment, auth, security, database
-})
-```
-
-### Step 2: Review Response
-
-The conflict check returns:
-- **Matching directives** — user rules that may prohibit the action
-- **Matching patterns** — past experiences relevant to this action
-- **Risk level** — safe, caution, or blocked
-
-### Step 3: Act Based on Result
-
-**If BLOCKED:** Do NOT proceed. Inform the user why.
-
-**If CAUTION:** Present the conflict to the user and ask for confirmation before proceeding.
-
-**If SAFE:** Proceed normally.
-
-## Example
-
-```
-User: "Drop the users table and recreate it"
-
-You: Let me check for conflicts first...
-
-ekkOS_Conflict({
-  proposed_action: "DROP TABLE users and recreate",
-  scope: "database"
-})
-
-Result: CAUTION — Directive found: "NEVER drop tables in production without backup"
-
-"⚠️ I found a directive: 'NEVER drop tables in production without backup.'
-Should I create a backup first, or is this a development database?"
-```
-
-## Integration with Golden Loop
-
-Safety checks are part of Step 1 (SEARCH) — they query the directive layer (L9) specifically. If a safety check prevents an accident, forge it:
-
-```
-ekkOS_Forge({
-  title: "Always backup before DROP TABLE",
-  problem: "Nearly dropped production table without backup",
-  solution: "ekkOS_Conflict caught the directive — always check first"
-})
-```
-
-Record the outcome:
-```
-ekkOS_Outcome({ success: true })  // Safety check prevented accident
-```
-
----
-
-**Mantra**: Measure twice, cut once. Check before destroying.

package/templates/windsurf-skills/ekkos-vault/SKILL.md

@@ -1,86 +0,0 @@
----
-name: ekkos-vault
-description: Securely store and retrieve credentials with AES-256-GCM encryption. Activate when the user shares an API key, password, token, secret, or any sensitive credential. Also activate when you need to use a stored credential or when the user asks about their stored secrets.
-allowed-tools:
-  - mcp__ekkos-memory__ekkOS_StoreSecret
-  - mcp__ekkos-memory__ekkOS_GetSecret
-  - mcp__ekkos-memory__ekkOS_ListSecrets
-  - mcp__ekkos-memory__ekkOS_DeleteSecret
-  - mcp__ekkos-memory__ekkOS_RotateSecret
----
-
-# ekkOS Secrets Vault
-
-Securely store and retrieve credentials encrypted with AES-256-GCM.
-
-## When To Activate
-
-| Trigger | Action |
-|---------|--------|
-| User shares API key, token, password | Store it |
-| User asks "do you have my X key?" | Retrieve it |
-| Need a credential for an API call | Retrieve it |
-| User asks "what secrets do I have?" | List them |
-| User wants to update a credential | Rotate it |
-| User asks to remove a credential | Delete it |
-
-## Instructions
-
-### Store a Secret
-
-```
-ekkOS_StoreSecret({
-  service: "openai",
-  value: "sk-...",
-  type: "api_key",
-  description: "OpenAI API key for embeddings"
-})
-```
-
-**NEVER echo the secret value back to the user.** Confirm storage without revealing it.
-
-### Retrieve a Secret
-
-```
-ekkOS_GetSecret({
-  service: "openai",
-  masked: false    // true = shows first/last 4 chars only
-})
-```
-
-### List Secrets (Metadata Only)
-
-```
-ekkOS_ListSecrets()
-```
-
-Returns service names, types, and descriptions — never values.
-
-### Rotate a Secret
-
-```
-ekkOS_RotateSecret({
-  service: "openai",
-  newValue: "sk-new-..."
-})
-```
-
-### Delete a Secret
-
-```
-ekkOS_DeleteSecret({
-  secretId: "<id from list>"
-})
-```
-
-## Security Rules
-
-1. **NEVER** display raw secret values in responses unless the user explicitly asks
-2. **NEVER** log secret values
-3. Use `masked: true` when you just need to confirm a secret exists
-4. When storing, confirm success WITHOUT echoing the value
-5. Secrets are encrypted at rest with AES-256-GCM — even ekkOS cannot read them without the user's key
-
----
-
-**Mantra**: Secrets go in the vault. Never in the chat.