From lc-essentials
Fetches LimaCharlie documentation from GitHub repositories using WebFetch for platform features, SDKs, APIs, D&R rules, LCQL, sensors, outputs, extensions, integrations, AI skills, agents.
npx claudepluginhub refractionpoint/lc-ai --plugin lc-essentialsThis skill is limited to using the following tools:
Use this skill proactively whenever a user asks about LimaCharlie features, configuration, or implementation.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.
Use this skill proactively whenever a user asks about LimaCharlie features, configuration, or implementation.
Invoke this skill when users ask about:
Documentation is fetched from two GitHub repositories using WebFetch:
| Repository | Base URL |
|---|---|
| Platform docs | https://raw.githubusercontent.com/refractionPOINT/documentation/master/ |
| AI skills/agents | https://raw.githubusercontent.com/refractionPOINT/lc-ai/master/ |
ALWAYS start by fetching index/navigation files to discover the current structure:
# For platform documentation - fetch the main index
WebFetch: https://raw.githubusercontent.com/refractionPOINT/documentation/master/docs/index.md
# For AI skills/agents - fetch the summary files
WebFetch: https://raw.githubusercontent.com/refractionPOINT/lc-ai/master/marketplace/plugins/lc-essentials/README.md
WebFetch: https://raw.githubusercontent.com/refractionPOINT/lc-ai/master/marketplace/plugins/lc-essentials/SKILLS_SUMMARY.md
These index files contain links to all available documentation. Parse the links to discover:
After fetching index files, extract the file paths from links in the markdown content:
[text](path/to/file.md) or [:icon: text](path/to/file.md)Based on what you discovered in the index files, fetch the specific documentation:
# Construct URLs dynamically from discovered paths
WebFetch: {base_url}/{discovered_path}
Fetch multiple relevant files in parallel - don't stop at one file.
User: "How do I write D&R rules?"
1. Discover structure:
WebFetch: https://raw.githubusercontent.com/refractionPOINT/documentation/master/docs/index.md
-> Parse the markdown to find links related to "Detection", "Response", "D&R", "rules"
-> Discover paths like: limacharlie/doc/Detection_and_Response/detection-and-response-rules.md
2. Fetch discovered docs (in parallel):
WebFetch: https://raw.githubusercontent.com/refractionPOINT/documentation/master/docs/{discovered_path_1}
WebFetch: https://raw.githubusercontent.com/refractionPOINT/documentation/master/docs/{discovered_path_2}
(paths extracted from index file links)
3. Respond with comprehensive answer combining all sources