Put your AI on a Performance Improvement Plan. Forces exhaustive problem-solving with Western big-tech performance culture rhetoric and structured debugging. Trigger when: (1) task failed 2+ times or stuck tweaking same approach; (2) about to say 'I cannot', suggest manual work, or blame environment without verifying; (3) being passive—not searching, not reading source, just waiting; (4) user frustration: 'try harder', 'stop giving up', 'figure it out', 'again???', or similar. Also for complex debugging, env issues, config/deployment failures. All task types: code, config, research, writing, deployment, infra, API. Do NOT trigger on first-attempt failures or when a known fix is executing.
- 📁 skills/
- 📁 src/
- 📄 index.ts
- 📄 INSTALL_OPENCLAW.md
- 📄 INSTALL_OPENCLAW_zh.md
This plugin is a thin adapter between OpenClaw and LycheeMem. It does not replace `memory-core`, does not claim `plugins.slots.memory`, and does not duplicate LycheeMem algorithms.
Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.
Use this skill ONLY when the user has a failing integration that is specifically based on an Afro.tools spec — the user is integrating a provider whose spec exists in the Afro.tools registry (Paycard, LengoPay, Djomy, Wave, NimbaSMS, etc.) and encounters wrong status codes, auth errors, webhook failures, unexpected response fields, or runtime errors. Do NOT activate for generic debugging, non-afrotools providers, or integrations not based on an Afro.tools spec. This skill diagnoses whether the problem is a spec error, a missing gotcha, or an undocumented API change. --- # Afro.tools — Debug skill When this skill activates, fetch the spec for the affected provider and capability, then systematically compare it against the user's implementation to find the gap. ## Workflow 1. Identify the provider slug and capability from the error, code snippet, or user description. Ask if unclear — don't guess. 2. Fetch the spec: ``` afrotools.get_spec({ provider: "<slug>", capability: "<capability>" }) ``` 3. **Check gotchas first.** Most integration failures map directly to a documented gotcha. Read every entry before looking elsewhere. 4. Cross-check the implementation against the spec: - **Auth** — correct field name, location (header vs body), format string - **Endpoint** — correct method and URL, path params in the right place - **Field names** — provider fields are often non-standard (e.g. `paycard-amount`, not `amount`); compare the user's payload against `input_schema` - **Status values** — enums are case-sensitive (e.g. LengoPay uses `SUCCESS`, not `success`); `code: 0` on Paycard means "found", not "paid" - **Webhook** — returning HTTP 200 immediately, not fulfilling on callback alone, HTTPS required for some providers 5. Surface the diagnosis clearly: - Quote the relevant spec field or gotcha - Show what the code does vs. what the spec requires - Provide a minimal corrected snippet
Publishes and updates remote Canvas pages on Acquia Source via Source MCP — images, props, layout; page JSON does not CLI-sync to Source. --- # Acquia Source — Canvas pages via Source MCP ## When this applies Use this skill when **all** of the following hold: 1. The target is an **Acquia Source** Drupal/Canvas site (see hostname signal and **`CANVAS_SITE_URL`** in [`AGENTS.md`](../../../AGENTS.md)). 2. The work is **Canvas pages** on the **remote** site (create page, place components, update layout/props, publish)—not local-only Workbench preview. ## Do not use Canvas CLI for remote pages **`canvas push` / `canvas pull` do not support syncing page JSON to/from the remote Acquia Source environment today.** Do not instruct users to rely on CLI page sync for that tenant. - **Components:** Continue to use the Canvas CLI (`npx canvas push`) and [`canvas-component-push`](../canvas-component-push/SKILL.md) for pushing **JavaScript components** when the user asks to push component source. - **Pages:** Use **Source MCP tools** on the configured server. ## Images and media (pages do not CLI-sync) Because **`canvas push` / `canvas pull` do not sync page JSON** to Acquia Source, **nothing in repo `pages/*.json` automatically provisions files or image props on the remote site.** Local page specs may use HTTPS placeholders, `placehold.co`, or example paths so **Workbench** renders; those values are not reliable as the remote source of truth. Treat image handling as a **remote-only** concern: ### What to do instead 1. **Discover the prop shape** — Each component’s `component.yml` defines how image fields are modeled (`image`, `heroImage`, nested objects, etc.). Keep that shape when updating instances on the server. 2. **Obtain Drupal-hosted media** — Prefer assets that live on the Source site: - **Upload** — Use Source MCP (`create_media` + signed upload URL pattern, etc.—read the live tool schema). See **Phase A5** in [`acquia-source-site-build`](../acquia-source-site-build/SKILL
Reference template for PopKit skill authoring. Not a runnable skill — lives under docs/skill-template/ so it is excluded from the skill scanner. Use when starting a new skill or refactoring an existing one to the standard. Do NOT copy verbatim without replacing every <placeholder>.
Quick URL bookmark capture : paste a link, AI generates name and description, suggests category, saves to Bookmarks.md in awesome-list format. Invoke when user wants to save a URL for later — bare URL with no other context defaults to this. Do NOT use for: deeply processing or summarizing the URL content now (use summarize), saving a note that is not a URL (use capture), or researching a topic from scratch (use research).
Quick URL bookmark capture : paste a link, AI generates name and description, suggests category, saves to Bookmarks.md in awesome-list format. Invoke when user wants to save a URL for later — bare URL with no other context defaults to this. Do NOT use for: deeply processing or summarizing the URL content now (use summarize), saving a note that is not a URL (use capture), or researching a topic from scratch (use research).
ADC uses **CSS custom properties** + **Tailwind v4 `@theme` directive** + **`color-mix()`** for a multi-theme, light/dark design system. Not shadcn defaults. Not Next.js patterns.
Use this skill whenever working with QuestDB — a high-performance time-series database. Trigger on any mention of QuestDB, time-series SQL with SAMPLE BY, LATEST ON, ASOF JOIN, ILP ingestion, or the questdb Python/Go/Java/Rust/.NET client libraries. Also trigger when writing Grafana queries against QuestDB, creating materialized views for time-series rollups, working with order book or financial market data in QuestDB, or any SQL that involves designated timestamps or time-partitioned tables. QuestDB extends SQL with unique time-series keywords — standard PostgreSQL or MySQL patterns will fail. Always read this skill before writing QuestDB SQL to avoid hallucinating incorrect syntax. --- # QuestDB Skill ## How to Use This Skill **IMPORTANT — MINIMIZE ROUND-TRIPS:** - Do NOT explore library source code (cryptofeed, questdb, etc.) - Do NOT check library versions or verify callback signatures - Do NOT read installed package files to "understand the API" - Do NOT verify infrastructure (Docker containers, Grafana health) is running — trust the user's prompt - Do NOT start `02_ingest.py` separately — `03_dashboard.py` launches it and verifies data automatically - Do NOT read extra reference files for topics already covered in this skill file - DO read reference files when their topic applies (e.g. enterprise.md for auth, grafana-advanced.md for complex panels) - Do NOT use task tracking (TaskCreate/TaskUpdate) for straightforward builds - Do NOT add `sleep` commands to wait for data or check background processes (the deploy script handles this) - Do NOT Ctrl+C, restart, or re-launch the ingestion process once `03_dashboard.py` has started it - Do NOT put VWAP, Bollinger, or RSI in separate timeseries panels — they are refIDs on the OHLC candlestick panel - Do NOT omit or empty `fieldConfig.overrides` — they put RSI on a right Y-axis (0-100%) and spread on a right axis. Without them, different scales crush the chart flat. - Do NOT set dashboard refresh to `"5s"` — the defa
- 📁 evals/
- 📁 references/
- 📄 SKILL.md
Explore ideas, clarify goals, and help the user narrow down directions before planning or coding. Use this whenever the user proposes a new feature or idea, asks "what do you think about X", says "I'm thinking of building Y", wants to compare approaches, asks how to approach a problem, or seems to be exploring rather than ready to execute. Also use it when the user says "brainstorm", "let's think about this", "what's the best way to...", or any time the right next step is to clarify the problem and converge on a direction, not to write code yet. --- # Brainstorm Before anything else, ask. Don't jump to solutions or implementation. The goal is to draw out what the user actually means, uncover what they have not said yet, and help them converge on a direction. Think of this as Socratic dialogue with momentum: use questions to guide the thinking, but do not leave the user wandering in options forever. ## Start With Context Before asking, absorb the context that already exists in the conversation, codebase, docs, and project state. Do not ask for information you can already infer or look up directly. ## Guide The Conversation
