This skill should be used when the user wants to visualize data. It intelligently selects the most suitable chart type from 26 available options, extracts parameters based on detailed specifications, and generates a chart image using a JavaScript script.
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.
End-to-end smoke test skill for Nova. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke test deployment", "verify installation", "test service availability", "end-to-end test", or similar.
Master skill for all Nova/DeerFlow agent work. Use this skill whenever you are building full-stack apps WITH Nova's computer agent (scaffold → verify → green loop), working ON Nova itself (middleware, harness, sprint patterns, journal hooks), or diagnosing Nova's agent-computer pipeline (white preview, 409, crash-loop, panel bugs, Stop not working). Routes to specialized references: build-loop (P1–P5 deterministic build), maintain (harness/middleware/sprint), diagnose (pipeline regressions). Triggers on: 'build me a...', 'I'm getting a 409', 'white preview', 'browser tab is blank', 'stop not working', 'add middleware', 'new sprint', 'harness boundary', 'extend Nova', 'run dev_verify', 'why is the agent stuck', 'the panel is clipped', 'BUILD_JOURNAL', 'drive to green'. Use this skill proactively — if the task touches Nova's codebase or uses Nova to build something, this skill applies.
Run Nova locally end-to-end (Docker Compose + PM2 + dev-entrypoint.sh). Use when the user says "how do I run this", "start Nova", "make dev", "spin it up locally", or "I just cloned the repo". Goes through pre-flight (Docker, PM2, uv, pnpm checks) → `make dev` → nginx :2026 + gateway :8001 + frontend :3000 → verification (curl `/`, curl `/health`, curl `/workspace/chats/<id>`). The canonical local dev path: `make dev` starts `docker compose -f docker/docker-compose-dev.yaml -f docker/docker-compose.dood.yaml up` under PM2 supervision. Triggers on phrases like "run Nova locally", "make dev", "I just cloned the repo", "first time setup".
Author or wire a new hook emission in Nova's LangChain agent loop. Use when adding observability for a new tool, when promoting a logged audit event to a structured receipt, or when extending the agent's self-evaluation storage. Nova's hook surface today is `RunJournal` (`backend/packages/harness/deerflow/runtime/journal.py:38`) which implements `BaseCallbackHandler` (on_tool_start / on_tool_end / on_chain_start / on_chain_end); there is no separate `PreToolUse`/`PostToolUse` enum, so any new hook emission must go through `RunJournal.record_middleware` or a new `BaseCallbackHandler` subclass. Triggers on phrases like "add observability for X", "log when tool Y runs", "instrument Z", or before shipping any new middleware.
Diagnose and fix a loop-detection firing in Nova's agent run. Use when the user reports "the agent keeps doing the same thing", "agent is stuck in ENOENT hell", or "we hit loop detection again" — also when reading the run's `[self-test]` lines shows repeated identical tool calls or ENOENT-style grep/searches. Triages across Layer 1 (hash-based), Layer 2 (per-tool frequency), Layer 3 (dead-end search divergence) per `backend/packages/harness/deerflow/agents/middlewares/loop_detection_middleware.py:837` and recommends the next code change. Triggers on phrases like "loop fired", "agent is repeating", "ENOENT pattern", or after observing a loop in the Activity tab.
Edit the lead agent's system prompt with discipline. Use when the user says "the agent is being too X", "tell the agent to Y", "the prompt needs a rule about Z", or before adding any new rule to the system prompt. The system prompt is at `backend/packages/harness/deerflow/agents/lead_agent/prompt.py` (a single function that returns a `ChatPromptTemplate`). Use this skill BEFORE making the change; the skill walks through the change-and-validate cycle. Triggers on phrases like "edit the agent prompt", "add a rule to the lead agent", "system prompt", "AGENT_MANIFEST", or before merging any change touching `agents/lead_agent/prompt.py`.