@harshitj183/ai-skills 2.2.7 → 2.2.8

package/skills/ai_history_maintenance.md

@@ -1,41 +1,46 @@
----
-name: "🤖 AI History Maintenance Skill"
-description: "This skill provides mandatory instructions for AI agents working on the `@harshitj183/ai-skills` pro"
----
-
-# 🤖 AI History Maintenance Skill
-
-This skill provides mandatory instructions for AI agents working on the `@harshitj183/ai-skills` project to maintain project history and transparency.
-
----
-
-## 🧐 Skill Summary
-Empowers AI agents to systematically document their actions, changes, and milestones within the project's dedicated `history/CONTEXT.md` system.
-
-## 🛠️ Implementation Guide
-
-### 1. Mandatory Updates
-After completing any major task (e.g., adding a new skill, fixing a bug, updating configurations), you **MUST** update the master context file:
-- **`history/CONTEXT.md`**: Append or update the relevant section with your AI name, date, and a bulleted list of tasks performed or changes made.
-
-### 2. Format and Tone
-- Use professional, clear markdown.
-- Maintain structured sections (e.g., Activity Log, System Architecture, Current Status).
-- Include dates in `YYYY-MM-DD` or `Month DD, YYYY` format in the Activity Log section.
-- Always sign the update with `*Last updated by: AI Assistant (<Name>)*`.
-
-### 3. Verification
-Before concluding any session, verify that:
-- The `history/CONTEXT.md` file accurately reflects the current state of the project.
-- No other scattered history files are created, maintaining the single-file context principle.
-
-## 🌟 Best Practices
-- **Proactive Documentation**: If you see a gap in history, fill it immediately in `CONTEXT.md`.
-- **Continuous Logging**: Update logs incrementally during long-running tasks.
-- **Context Awareness**: Read the `CONTEXT.md` file at the start of any new session to understand previous work and milestones.
-
----
-*Signed: AI History Architect*
-
----
-⚡ Smart AI Skills Library | v2.2.7 | Active
+---
+name: "🤖 AI History Maintenance Skill"
+description: "This skill provides mandatory instructions for AI agents working on the `@harshitj183/ai-skills` project to maintain history."
+---
+
+# 🤖 AI History Maintenance Skill
+
+This skill provides mandatory instructions for AI agents working on the `@harshitj183/ai-skills` project to maintain project history and transparency.
+
+---
+
+## 🧐 Skill Summary
+Empowers AI agents to systematically document their actions, changes, and milestones within the project's dedicated `history/CONTEXT.md` system.
+
+## 🛠️ Implementation Guide
+
+### 1. Mandatory Updates
+After completing any major task (e.g., adding a new skill, fixing a bug, updating configurations), you **MUST** update the master context file:
+- **`history/CONTEXT.md`**: Append or update the relevant section with your AI name, date, and a bulleted list of tasks performed or changes made.
+
+### 2. Format and Tone
+- Use professional, clear markdown.
+- Maintain structured sections (e.g., Activity Log, System Architecture, Current Status).
+- Include dates in `YYYY-MM-DD` or `Month DD, YYYY` format in the Activity Log section.
+- Always sign the update with `*Last updated by: AI Assistant (<Name>)*`.
+
+### 3. Verification
+Before concluding any session, verify that:
+- The `history/CONTEXT.md` file accurately reflects the current state of the project.
+- No other scattered history files are created, maintaining the single-file context principle.
+
+## 🌟 Best Practices
+- **Proactive Documentation**: If you see a gap in history, fill it immediately in `CONTEXT.md`.
+- **Continuous Logging**: Update logs incrementally during long-running tasks.
+- **Context Awareness**: Read the `CONTEXT.md` file at the start of any new session to understand previous work and milestones.
+
+### 4. Data Sensitivity & Privacy (CRITICAL)
+- **NO PII/Secrets**: Never write API keys, passwords, bearer tokens, or sensitive Personally Identifiable Information (PII) to `CONTEXT.md` or logs.
+- **Abstract Logic**: Describe *what* you did (e.g., "Updated auth logic") rather than showing the literal credentials or private data.
+- **Audit Logs**: If you accidentally log a secret, rotate it immediately and scrub the history files.
+
+---
+*Signed: AI History Architect*
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/anthropic_documents.md

@@ -1,16 +1,16 @@
----
-name: "Anthropic Documents Expert"
-description: "Rules for parsing and extracting knowledge from DOCX, PDF, PPTX, and XLSX."
----
-
-# Precision Extraction
-1. **XLSX Logic:** Always process wide spreadsheets by streaming rows instead of loading an entire massive matrix into context. Evaluate column data types stringently before outputting schemas.
-2. **PPTX Analysis:** Do not hallucinate chart data. If parsing images or slides within a PPTX, declare explicitly standard structural points (Slide 1: Title, Slide 2: Bullet points).
-3. **PDF OCR:** Treat raw PDF text extraction as potentially prone to bad spacing. Never match exact string comparisons across multi-line breaks. Use regex `/[\s\S]*/` matching cautiously.
-
-# Document Editing
-- When co-authoring or restructuring, maintain the exact tone of the input document explicitly unless specified to rewrite. 
-- Return final edits as clean Markdown mapping strictly to Word Headers (H1, H2, H3).
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "Anthropic Documents Expert"
+description: "Rules for parsing and extracting knowledge from DOCX, PDF, PPTX, and XLSX."
+---
+
+# Precision Extraction
+1. **XLSX Logic:** Always process wide spreadsheets by streaming rows instead of loading an entire massive matrix into context. Evaluate column data types stringently before outputting schemas.
+2. **PPTX Analysis:** Do not hallucinate chart data. If parsing images or slides within a PPTX, declare explicitly standard structural points (Slide 1: Title, Slide 2: Bullet points).
+3. **PDF OCR:** Treat raw PDF text extraction as potentially prone to bad spacing. Never match exact string comparisons across multi-line breaks. Use regex `/[\s\S]*/` matching cautiously.
+
+# Document Editing
+- When co-authoring or restructuring, maintain the exact tone of the input document explicitly unless specified to rewrite. 
+- Return final edits as clean Markdown mapping strictly to Word Headers (H1, H2, H3).
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/antigravity_mastery.md

@@ -1,15 +1,15 @@
----
-name: "Antigravity OS & Workflow Mastery"
-description: "Advanced interaction rules for CLI invocation, bash routing, and OS-level operations."
----
-
-# CLI Orchestration
-1. **Parallel Tooling:** Maximize parallel CLI invocations using `run_command` concurrently across batch jobs if states don't mutually conflict.
-2. **Terminal Scraping:** Never use raw `cat` for files larger than 1000 lines. Default to `grep_search` and `view_content_chunk` to prevent context explosion.
-3. **Activation Scripts:** Handle agent overload gracefully in Windows/Linux by slicing stdout responses and avoiding infinite crash loops in stderr rendering.
-
-# Workflow Bundling
-- Construct workflows as strict YAML-frontmatter markdown files with `// turbo` tags to permit specific safe auto-execution loops for repetitive tasks.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "Antigravity OS & Workflow Mastery"
+description: "Advanced interaction rules for CLI invocation, bash routing, and OS-level operations."
+---
+
+# CLI Orchestration
+1. **Parallel Tooling:** Maximize parallel CLI invocations using `run_command` concurrently across batch jobs if states don't mutually conflict.
+2. **Terminal Scraping:** Never use raw `cat` for files larger than 1000 lines. Default to `grep_search` and `view_content_chunk` to prevent context explosion.
+3. **Activation Scripts:** Handle agent overload gracefully in Windows/Linux by slicing stdout responses and avoiding infinite crash loops in stderr rendering.
+
+# Workflow Bundling
+- Construct workflows as strict YAML-frontmatter markdown files with `// turbo` tags to permit specific safe auto-execution loops for repetitive tasks.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/azure_graph_integrator.md

@@ -1,12 +1,12 @@
----
-name: "Microsoft Graph & Azure Integrator"
-description: "Rules for Azure AD tokens, Graph API requests, and Enterprise app setup."
----
-
-# Graph API Best Practices
-1. **Token Scopes:** Request explicit `Mail.ReadWrite`, `User.Read` only based on what the application specifically mutates. Never use `Directory.ReadWrite.All` carelessly.
-2. **Pagination Enforcement:** Implement strictly `odata.nextLink` tracking when querying users or large resource collections.
-3. **Batching:** Reduce network overhead by clustering up to 20 sub-requests via `/$batch` endpoints when orchestrating multi-user mutations.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "Microsoft Graph & Azure Integrator"
+description: "Rules for Azure AD tokens, Graph API requests, and Enterprise app setup."
+---
+
+# Graph API Best Practices
+1. **Token Scopes:** Request explicit `Mail.ReadWrite`, `User.Read` only based on what the application specifically mutates. Never use `Directory.ReadWrite.All` carelessly.
+2. **Pagination Enforcement:** Implement strictly `odata.nextLink` tracking when querying users or large resource collections.
+3. **Batching:** Reduce network overhead by clustering up to 20 sub-requests via `/$batch` endpoints when orchestrating multi-user mutations.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/coderabbit_review.md

@@ -0,0 +1,36 @@
+---
+name: "CodeRabbit Reviewer"
+description: "High-precision, strict code review agent focusing on architectural patterns, clean code (SOLID/DRY), and premium design integrity."
+---
+
+# 1. Review Methodology
+The CodeRabbit persona is **Proactive**, **Opinionated**, and **Technical**. It does skip surface-level linting to focus on deep logic.
+
+- **PR Summary**: Automatically generate a "What," "Why," and "How" summary of changes.
+- **Line-by-line Critique**: Provide specific, actionable code suggestions (not just complaints).
+- **Security & Performance**: Audit for potential leaks, race conditions, or O(n) disasters.
+
+# 2. Logic Flow
+```mermaid
+graph TD
+    A[Start Review] --> B{Analyze Diff}
+    B --> C[Check Architectural Consistency]
+    B --> D[Identify Code Smells]
+    B --> E[Security/Auth Audit]
+    C & D & E --> F[Synthesize Review]
+    F --> G[Generate PR Summary]
+    G --> H[Inline Suggestions]
+    H --> I[Final 'Approve' or 'Request Changes']
+```
+
+# 3. Constraints & Personas
+- **Stricter than Humans**: If a loop can be a map, suggest it. If a variable is shadowed, flag it.
+- **Design Awareness**: Specifically for frontend, flag any deviations from established CSS tokens or glassmorphism standards.
+- **No Fluff**: No "Good job" without technical justification. Focus on refinement.
+
+# 4. Trigger Commands
+- `Review with CodeRabbit`: Triggers full audit.
+- `CodeRabbit, check this logic`: Focuses on a specific block.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/composio_integrator.md

@@ -1,16 +1,16 @@
----
-name: "Composio App Orchestrator"
-description: "Rules for integrating Claude with 500+ apps using ComposioHQ."
----
-
-# Integration Guidelines
-1. **Authentication Handling:** Never expose OAuth keys directly. Rely entirely on Composio's managed authentication gateway via the Composio Plugin.
-2. **Entity Management:** Whenever triggering cross-platform actions (e.g., Salesforce to Jira), link requests using fixed Composio `entity_id` values.
-3. **Action Triggers:** Do not guess the API schemas. Use Composio's SDK `composio.executeAction(Action.GITHUB_CREATE_ISSUE, { ... })` for strongly-typed integrations.
-
-# Security
-- Ensure strict least-privilege scoping when generating the Composio connection links.
-- Treat every response payload as untrusted and sanitize before feeding into downstream actions.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "Composio App Orchestrator"
+description: "Rules for integrating Claude with 500+ apps using ComposioHQ."
+---
+
+# Integration Guidelines
+1. **Authentication Handling:** Never expose OAuth keys directly. Rely entirely on Composio's managed authentication gateway via the Composio Plugin.
+2. **Entity Management:** Whenever triggering cross-platform actions (e.g., Salesforce to Jira), link requests using fixed Composio `entity_id` values.
+3. **Action Triggers:** Do not guess the API schemas. Use Composio's SDK `composio.executeAction(Action.GITHUB_CREATE_ISSUE, { ... })` for strongly-typed integrations.
+
+# Security
+- Ensure strict least-privilege scoping when generating the Composio connection links.
+- Treat every response payload as untrusted and sanitize before feeding into downstream actions.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/github_automation.md

@@ -1,17 +1,17 @@
----
-name: "GitHub Automation Expert"
-description: "Rules for branching, merging, rebasing, CI/CD Actions, and PR generation."
----
-
-# Git Workflow
-1. **Commit Messages:** Follow Conventional Commits format exactly: `feat(scope): message` or `fix(scope): message`.
-2. **Rebasing:** Prefer rebasing over merge commits to keep the history linear. Warn against rebasing public branches.
-3. **Conflict Resolution:** Never just guess. Always evaluate `<<<<<<< HEAD` blocks contextually based on recent timeline logic.
-
-# GitHub Actions
-- Keep workflows DRY. Use reusable workflows or composite actions for repeating test steps.
-- Set explicit read/write permissions for `GITHUB_TOKEN`.
-- Optimize action caching mapping (e.g. `actions/cache` or `setup-node` caching).
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "GitHub Automation Expert"
+description: "Rules for branching, merging, rebasing, CI/CD Actions, and PR generation."
+---
+
+# Git Workflow
+1. **Commit Messages:** Follow Conventional Commits format exactly: `feat(scope): message` or `fix(scope): message`.
+2. **Rebasing:** Prefer rebasing over merge commits to keep the history linear. Warn against rebasing public branches.
+3. **Conflict Resolution:** Never just guess. Always evaluate `<<<<<<< HEAD` blocks contextually based on recent timeline logic.
+
+# GitHub Actions
+- Keep workflows DRY. Use reusable workflows or composite actions for repeating test steps.
+- Set explicit read/write permissions for `GITHUB_TOKEN`.
+- Optimize action caching mapping (e.g. `actions/cache` or `setup-node` caching).
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/hashicorp_terraform.md

@@ -1,16 +1,16 @@
----
-name: "HashiCorp Terraform Auto-Deployer"
-description: "HCL code generation and AWS/GCP Provider orchestration."
----
-
-# Terraform Module Generation
-1. **State Isolation:** Never use a single unified `apply` for an entire company stack. Isolate state using Workspaces or entirely separate `prod/`, `staging/` directories.
-2. **Data Variables:** Hardcode absolutely nothing. Use `variables.tf` heavily and separate environment tiers via `terraform.tfvars`.
-3. **Provider Pinning:** Always pin provider versions inside the `required_providers` block block to prevent breaking API changes from propagating automatically.
-
-# Best Practices
-- Output strictly what is necessary (e.g., Load Balancer URLs) to prevent leaking exact subnet or SG configurations.
-- Default to `for_each` over `count` when looping to avoid shifting indices issues upon list modifications.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "HashiCorp Terraform Auto-Deployer"
+description: "HCL code generation and AWS/GCP Provider orchestration."
+---
+
+# Terraform Module Generation
+1. **State Isolation:** Never use a single unified `apply` for an entire company stack. Isolate state using Workspaces or entirely separate `prod/`, `staging/` directories.
+2. **Data Variables:** Hardcode absolutely nothing. Use `variables.tf` heavily and separate environment tiers via `terraform.tfvars`.
+3. **Provider Pinning:** Always pin provider versions inside the `required_providers` block block to prevent breaking API changes from propagating automatically.
+
+# Best Practices
+- Output strictly what is necessary (e.g., Load Balancer URLs) to prevent leaking exact subnet or SG configurations.
+- Default to `for_each` over `count` when looping to avoid shifting indices issues upon list modifications.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/letta_agent_memory.md

@@ -1,15 +1,15 @@
----
-name: "Letta Agent Memory Manager"
-description: "Rules for long-term memory management, persistent context, and core Letta-style memory blocks."
----
-
-# Core Memory Blocks
-1. **Persona Update:** Agents must actively call `core_memory_append` to update their understanding of the user state or global variable states.
-2. **Archival Memory:** Use archival search strategies for infinite-context scrolling. Avoid overloading context windows.
-3. **Context Truncation Alert:** Always respond gracefully if `warning_context_limit` triggers by summarizing preceding events into the core memory block and continuing.
-
-# Best Practices
-- Agents run indefinitely. Maintain context continuity strictly via memory, never rely on conversation history alone.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "Letta Agent Memory Manager"
+description: "Rules for long-term memory management, persistent context, and core Letta-style memory blocks."
+---
+
+# Core Memory Blocks
+1. **Persona Update:** Agents must actively call `core_memory_append` to update their understanding of the user state or global variable states.
+2. **Archival Memory:** Use archival search strategies for infinite-context scrolling. Avoid overloading context windows.
+3. **Context Truncation Alert:** Always respond gracefully if `warning_context_limit` triggers by summarizing preceding events into the core memory block and continuing.
+
+# Best Practices
+- Agents run indefinitely. Maintain context continuity strictly via memory, never rely on conversation history alone.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/lifecycle/brainstorming.md

@@ -1,24 +1,58 @@
----
-name: "Idea-to-Spec Workflow"
-description: "High-fidelity brainstorming to transform raw user ideas into technical specifications."
----
-
-# 1. Brainstorming Logic
-When a user provides a raw idea or a vague request:
-- **Challenge Assumptions**: Ask "Why?" and "What is the core user pain point?".
-- **Constraint Identification**: List what is NOT being built.
-- **Architectural Mapping**: Determine which `roles/` and `skills/` from the library will be needed for this feature.
-
-# 2. Output: The Micro-Spec
-- **Goal**: One sentence.
-- **Features**: Bullet list of MUST-HAVEs.
-- **Edge Cases**: Identify 3-5 failure modes.
-- **Plan**: Hand-off to `skills/orchestration/plan_architect.md`.
-
-# 3. Collaborative Loop
-- Present the Micro-Spec to the user.
-- Incorporate one round of feedback.
-- Confirm final design before implementation.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "Idea-to-Spec Workflow"
+description: "High-fidelity brainstorming to transform raw user ideas into technical specifications."
+---
+
+# 1. Ideation Flow
+
+```mermaid
+graph LR;
+    A[Idea/Problem] --> B[Stakeholder Needs];
+    B --> C[Constraint Mapping];
+    C --> D[Solution Drafting];
+    D --> E[Feasibility Check];
+    E --> F[Core Spec];
+```
+
+# 1. Protocol Logic
+When a user provides a raw idea or a vague request:
+- **Challenge Assumptions**: Ask "Why?" and "What is the core user pain point?".
+- **Constraint Identification**: List what is NOT being built.
+- **Architectural Mapping**: Determine which `roles/` and `skills/` from the library will be needed for this feature.
+
+# 2. Review Protocol
+
+```mermaid
+sequenceDiagram
+    participant U as User
+    participant AI as System
+    AI->>U: Present Micro-Spec
+    U->>AI: Provide Feedback
+    AI->>AI: Refine Spec
+    AI->>U: Confirm Final Design
+```
+
+# 3. External Skill Retrieval
+
+```mermaid
+graph TD;
+    A[Task Requirement] --> B{Skill Library};
+    B -->|Match Found| C[Load Skill Module];
+    B -->|No Match| D[Generate Custom Logic];
+    C --> E[Execute Task];
+    D --> E[Execute Task];
+```
+
+# 4. Output: The Micro-Spec
+- **Goal**: One sentence.
+- **Features**: Bullet list of MUST-HAVEs.
+- **Edge Cases**: Identify 3-5 failure modes.
+- **Plan**: Hand-off to `skills/orchestration/plan_architect.md`.
+
+# 3. Collaborative Loop
+- Present the Micro-Spec to the user.
+- Incorporate one round of feedback.
+- Confirm final design before implementation.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/lifecycle/review_protocol.md

@@ -1,25 +1,36 @@
----
-name: "Code Review Protocol"
-description: "High-fidelity feedback loops and rigorous quality assurance."
----
-
-# 1. Review Request Logic
-When requesting review (from a human or another AI):
-- **PR Summary**: List changed files and their logical impact.
-- **Critical Points**: Explicitly point out complex logic or sensitive changes.
-- **Context Pack**: Provide the `SKILL.md` rules and the current `status_summary.md` as context.
-
-# 2. Receiving Review Logic
-When processing feedback:
-1. **Analyze**: Categorize by Impact (Critical, Minor, Nit).
-2. **Respond**: Acknowledge each point and provide the reasoning behind the fix.
-3. **Fix**: Use the `tdd_mastery.md` skill to safely implement any changes.
-4. **Verify**: Run the full test suite again.
-
-# 3. Quality Metrics
-- Zero-defect code.
-- No regression.
-- Performance impact <1%.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "Code Review Protocol"
+description: "High-fidelity feedback loops and rigorous quality assurance."
+---
+
+# 1. Review Flow
+
+```mermaid
+graph TD;
+    A[Output Draft] --> B[Self-Review];
+    B --> C[Logic Check];
+    C --> D[Security Audit];
+    D --> E[Persona Consistency];
+    E --> F[Final Submission];
+```
+
+# 1. Review Request Logic
+When requesting review (from a human or another AI):
+- **PR Summary**: List changed files and their logical impact.
+- **Critical Points**: Explicitly point out complex logic or sensitive changes.
+- **Context Pack**: Provide the `SKILL.md` rules and the current `status_summary.md` as context.
+
+# 2. Receiving Review Logic
+When processing feedback:
+1. **Analyze**: Categorize by Impact (Critical, Minor, Nit).
+2. **Respond**: Acknowledge each point and provide the reasoning behind the fix.
+3. **Fix**: Use the `tdd_mastery.md` skill to safely implement any changes.
+4. **Verify**: Run the full test suite again.
+
+# 3. Quality Metrics
+- Zero-defect code.
+- No regression.
+- Performance impact <1%.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/mcp_master.md

@@ -1,17 +1,17 @@
----
-name: "MCP Master Guidelines"
-description: "Rules for building Model Context Protocol (MCP) servers and tools."
----
-
-# MCP Architecture
-1. **Server Instantiation:** Always use `@modelcontextprotocol/sdk/server/index.js` and `StdioServerTransport`.
-2. **Schema Definition:** Define strictly typed input schemas using `zod` and map them to `ListToolsRequestSchema`.
-3. **Execution Handling:** Map each named tool to its logic block inside `CallToolRequestSchema`. Parse inputs rigorously.
-
-# Core Principles
-- Treat MCP tools as pure functions; inputs go in, localized results come out. No global state side-effects.
-- Provide comprehensive error handling. Never crash the stdio transport.
-- Return responses strictly in the format `[{ type: "text", text: resultString }]`.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "MCP Master Guidelines"
+description: "Rules for building Model Context Protocol (MCP) servers and tools."
+---
+
+# MCP Architecture
+1. **Server Instantiation:** Always use `@modelcontextprotocol/sdk/server/index.js` and `StdioServerTransport`.
+2. **Schema Definition:** Define strictly typed input schemas using `zod` and map them to `ListToolsRequestSchema`.
+3. **Execution Handling:** Map each named tool to its logic block inside `CallToolRequestSchema`. Parse inputs rigorously.
+
+# Core Principles
+- Treat MCP tools as pure functions; inputs go in, localized results come out. No global state side-effects.
+- Provide comprehensive error handling. Never crash the stdio transport.
+- Return responses strictly in the format `[{ type: "text", text: resultString }]`.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/memory_cycle.md

@@ -0,0 +1,45 @@
+---
+name: "Memory Cycle"
+description: "Archiving learned patterns and workflow insights from transient context into persistent history."
+---
+
+# 1. Memory Workflow
+
+```mermaid
+graph LR;
+    A[Session End] --> B[Extract Patterns];
+    B --> C[Evaluate Utility];
+    C -- High --> D[Archive to history/];
+    C -- Low --> E[Discard];
+    D --> F[Index Update];
+```
+
+# 1. Trigger Condition
+Activate this skill when:
+- A complex task is completed (e.g., successful bug fix after multiple attempts).
+- A new "Best Practice" or "Gotcha" is discovered for a specific technology.
+- The user expresses a strong preference for a specific style or logic pattern.
+
+# 2. Archival Protocol
+1. **Identify the Core**: Extract the specific logic or pattern that worked.
+2. **Standardize**: format the insight as a "Lesson Learned".
+3. **Persist**: 
+   - Append to `history/lessons.md` OR create a new file in `history/patterns/`.
+   - Update `history/ai_activity_log.md` with the archival event.
+4. **Cleanup**: Clear the transient session memory of redundant details while keeping the "Pointer" to the archived history.
+
+# 3. Lesson format
+```markdown
+## [Tech/Skill] - [Title]
+- **Date**: YYYY-MM-DD
+- **Context**: Problem description.
+- **Solution**: The specific pattern that worked.
+- **Why**: Rationale for why this is the preferred approach.
+```
+
+# 4. Success Criteria
+- Future sessions can refer to `history/` to avoid repeating errors.
+- The library "grows" smarter with every interaction.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active

package/skills/openai_structured_outputs.md

@@ -1,12 +1,12 @@
----
-name: "OpenAI Structured Outputs Expert"
-description: "Rules for extreme JSON schema strictness and function calling optimizations."
----
-
-# Function Calling Optimization
-1. **JSON Schema Strictness:** Enforce `strict: true` validation on all `response_format` JSON Schema definitions. Do not use generic `object` types without defined explicit properties.
-2. **Hallucination Prevention:** When returning enum arrays, reject all outputs not exactly mapping to the predefined subset.
-3. **System Prompt Alignment:** Embed function definitions within the system instruction block rather than heavily relying on implicit user prompts to guess shapes.
-
----
-⚡ Smart AI Skills Library | v2.2.6 | Active
+---
+name: "OpenAI Structured Outputs Expert"
+description: "Rules for extreme JSON schema strictness and function calling optimizations."
+---
+
+# Function Calling Optimization
+1. **JSON Schema Strictness:** Enforce `strict: true` validation on all `response_format` JSON Schema definitions. Do not use generic `object` types without defined explicit properties.
+2. **Hallucination Prevention:** When returning enum arrays, reject all outputs not exactly mapping to the predefined subset.
+3. **System Prompt Alignment:** Embed function definitions within the system instruction block rather than heavily relying on implicit user prompts to guess shapes.
+
+---
+⚡ Smart AI Skills Library | v2.2.8 | Active