Rewrite context-engine skill description for better discovery

Make trigger phrases explicit (CodeAlive, get data sources, list indexed
repos, semantic/grep search, fetch, call graphs), name the MCP tools the
skill wraps, and add an anti-fallback clause pointing agents at the skill
instead of curl or ToolSearch. Compact the body from ~470 to ~450 chars,
dropping redundant behavioral query examples.

Bump plugin to 2.0.4.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: rodion-m

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "codealive",
   "description": "CodeAlive context engine for semantic code search and AI-powered codebase Q&A. Enables AI coding agents to understand entire codebases beyond just open files — search across all indexed repositories, trace cross-service dependencies, discover usage patterns, and get synthesized answers to architectural questions. Includes a lightweight code exploration subagent, authentication hooks, and multiple search modes (fast lexical, semantic, and deep cross-cutting). Works standalone or alongside the CodeAlive MCP server for direct tool access via the Model Context Protocol.",
-  "version": "2.0.3",
+  "version": "2.0.4",
   "author": {
     "name": "CodeAlive AI",
     "email": "hello@codealive.ai"

skills/codealive-context-engine/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: codealive-context-engine
-description: Semantic code search and AI-powered codebase Q&A across indexed repositories. Use when understanding code beyond local files, exploring dependencies, discovering cross-project patterns, planning features, debugging, or onboarding. Queries like "How does X work?", "Show me Y patterns", "How is library Z used?". The default path is semantic search plus grep search; chat-with-codebase is slower, more expensive, and usually secondary.
+description: Semantic search, grep, and Q&A across codebases and documentation indexed in CodeAlive. Use when the user mentions "CodeAlive", asks to list or get data sources, list indexed repositories, search code or docs across repos, fetch artifact content, or trace call graphs. Wraps MCP tools get_data_sources, semantic_search, grep_search, fetch_artifacts, get_artifact_relationships. Invoke this instead of curling mcp.codealive.ai or running ToolSearch.
 ---
 
 # CodeAlive Context Engine