DeerFlow Smoke Test
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
This skill should be used when the user wants to report a bug, file an issue, or suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub).
$ npx skills add codemie-ai/codemie-code --skill report-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install codemie-ai/codemie-code report-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/agents/plugins/claude/plugin/skills/report-issue .claude/skills/report-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "report-issue" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/src/agents/plugins/claude/plugin/skills/report-issue into .claude/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/codemie-ai/codemie-code/tree/main/src/agents/plugins/claude/plugin/skills/report-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add codemie-ai/codemie-code --skill report-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install codemie-ai/codemie-code report-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/agents/plugins/claude/plugin/skills/report-issue .agents/skills/report-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "report-issue" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/src/agents/plugins/claude/plugin/skills/report-issue into .agents/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codemie-ai/codemie-code --skill report-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install codemie-ai/codemie-code report-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/agents/plugins/claude/plugin/skills/report-issue .cursor/skills/report-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "report-issue" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/src/agents/plugins/claude/plugin/skills/report-issue into .cursor/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/codemie-ai/codemie-code.git --path src/agents/plugins/claude/plugin/skills/report-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add codemie-ai/codemie-code --skill report-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install codemie-ai/codemie-code report-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/agents/plugins/claude/plugin/skills/report-issue .gemini/skills/report-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "report-issue" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/src/agents/plugins/claude/plugin/skills/report-issue into .gemini/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install codemie-ai/codemie-code report-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add codemie-ai/codemie-code --skill report-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/agents/plugins/claude/plugin/skills/report-issue .github/skills/report-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "report-issue" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/src/agents/plugins/claude/plugin/skills/report-issue into .github/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codemie-ai/codemie-code --skill report-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install codemie-ai/codemie-code report-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/agents/plugins/claude/plugin/skills/report-issue .opencode/skills/report-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "report-issue" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/src/agents/plugins/claude/plugin/skills/report-issue into .opencode/skills/report-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "report-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
report-issueThis skill should be used when the user wants to report a bug, file an issue, or suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub).
Report Issue is an agent skill from codemie-ai/codemie-code. This skill should be used when the user wants to report a bug, file an issue, or suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub). Trigger phrases include: "report a bug", "open an issue", "submit an issue", "file a bug report", "something is broken in CodeMie", "report to GitHub", "create a GitHub issue", "suggest a feature for CodeMie", "request an enhancement", "I have a feature idea", "codemie is not working", or any mention of filing a report for CodeMie. This…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering QA and bug reports. It works with GitHub and Node.js. The repository describes itself as: AI Run CodeMie CLI with analytics capabilities. The licence is Apache-2.0.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 0218c8d. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGrepFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghnodenpmbrewaptdnfwingetFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
gist.github.comAlso links to:
cli.github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Report Issue loads about 2.3k tokens when it runs. Until then it costs about 198 tokens; SKILL.md has 627 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
> - **Linux (apt)**: `sudo apt install gh`> - **Linux (dnf)**: `sudo dnf install gh`allowed-tools: Bash, Read, GrepAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from codemie-ai/codemie-code at commit 0218c8d, republished under its Apache-2.0 licence (© codemie-ai). 627 words, ~2,253 tokens.
.claude/skills/report-issue/SKILL.md (or your agent's skills folder).Help the user file a well-structured bug report or feature request to codemie-ai/codemie-code on GitHub.
The goal is to create a rich issue that gives maintainers everything they need to triage and reproduce the problem — without requiring the user to manually gather technical details.
gh CLI first — do this before anything elseif ! command -v gh &>/dev/null; then
echo "GH_NOT_INSTALLED"
else
gh auth status 2>&1 || echo "GH_NOT_AUTHENTICATED"
fiIf GH_NOT_INSTALLED: Stop immediately and tell the user:
"
gh(GitHub CLI) is not installed. It is required to create issues from the terminal.Install it with one of:
- macOS:
brew install gh- Linux (apt):
sudo apt install gh- Linux (dnf):
sudo dnf install gh- Windows:
winget install --id GitHub.cli- Or download from: https://cli.github.com
After installing, run
gh auth loginto connect your GitHub account, then try this skill again."
If GH_NOT_AUTHENTICATED: Stop and tell the user:
"
ghis installed but not authenticated. Rungh auth loginto connect to your GitHub account, then try again."
Do not proceed past this point until gh is installed and authenticated.
Run the following and capture results. Don't display raw output yet.
# OS + platform
uname -srm 2>/dev/null || echo "unknown"
# Node.js version
node --version 2>/dev/null || echo "not found"
# npm version
npm --version 2>/dev/null || echo "not found"
# CodeMie CLI version
codemie --version 2>/dev/null || echo "not found"
# Installed agents and versions
codemie list --installed 2>/dev/null || echo "unavailable"
# Full doctor output (profile, provider, dependency health, agent versions)
codemie doctor 2>/dev/null || echo "unavailable"
# Shell + terminal environment
echo "Shell: $SHELL"
echo "Terminal: ${TERM_PROGRAM:-unknown}"
# Extract ERROR and WARN lines from the two most recent log files.
# Log format: [TIMESTAMP] [LEVEL] [agent] [session-id] [profile] [component] message
# Files: ~/.codemie/logs/debug-YYYY-MM-DD.log (one per day, can be several MB)
LOG_DIR="$HOME/.codemie/logs"
RECENT_LOGS=$(ls -t "$LOG_DIR"/debug-*.log 2>/dev/null | head -2)
if [ -n "$RECENT_LOGS" ]; then
echo "=== ERROR and WARN entries from recent logs ==="
# Print filename headers and filter by level; limit to last 100 matches to keep size reasonable
for f in $RECENT_LOGS; do
echo "--- $f ---"
grep -E '\[(ERROR|WARN)\]' "$f" | tail -50
done
echo "=== Full log files ==="
for f in $RECENT_LOGS; do
echo "$f"
done
else
echo "No debug logs found"
fiLog file paths (captured above) will be used in Step 6 to upload as Gist.
Extraction-first: If the user already described the issue in their request (problem, error message, steps, etc.), extract that information directly without asking them to repeat it. Only ask follow-up questions for missing pieces.
If no description was provided yet, ask the user for:
When prompting for description, share these tips:
Determine the issue type based on the user's description:
bugenhancementquestionBuild the issue body using the appropriate template below.
Security — before embedding diagnostic output:
***)proxy-ha***dled already used by codemie doctor is safe to include as-is## Description
<user's description of the problem>
## Steps to Reproduce
1.
2.
3.
## Expected Behavior
<what the user expected to happen>
## Actual Behavior
<what actually happened — paste error messages verbatim>
## Environment
| Field | Value |
|-------------|------------------------------|
| OS | <uname output> |
| Node.js | <node --version> |
| npm | <npm --version> |
| CodeMie CLI | <codemie --version> |
| Shell | <$SHELL> |
| Terminal | <$TERM_PROGRAM> |
## Installed Agents
<formatted list from `codemie list --installed` — agent name and version per line>
## CodeMie Doctor Output
<details>
<summary>Full doctor output</summary>
<pre>
<codemie doctor output — with credentials redacted>
</pre>
</details>
## Recent Errors
<details>
<summary>ERROR and WARN entries from recent logs</summary>
<pre>
<filtered ERROR/WARN lines from the two most recent debug-YYYY-MM-DD.log files, or "No errors found">
</pre>
</details>
## Full Debug Logs
<full log file(s) attached as GitHub Gist — see link below, or "No log files found">## Summary
<one-sentence description of the feature>
## Motivation
<the problem this feature would solve, or the use case that is currently missing>
## Proposed Behavior
<what the user wants to happen — be specific about inputs, outputs, and commands>
## Alternatives Considered
<other ways you have worked around this, if any>
## Environment
| Field | Value |
|-------------|------------------------------|
| OS | <uname output> |
| Node.js | <node --version> |
| CodeMie CLI | <codemie --version> |
## Installed Agents
<formatted list from `codemie list --installed`>Show the user the proposed issue title and full body. Ask:
"Here's the issue I'll create on GitHub. Does this look right, or would you like to change anything before I submit?"
Wait for confirmation before creating the issue.
If log files were found in Step 1b, upload the two most recent ones as a secret Gist so they can be referenced in the issue. This keeps the issue body readable while giving maintainers the full context.
# Upload the two most recent log files as a single secret Gist
gh gist create \
--desc "CodeMie debug logs for issue report ($(date +%Y-%m-%d))" \
~/.codemie/logs/debug-$(date +%Y-%m-%d).log \
~/.codemie/logs/debug-$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d yesterday +%Y-%m-%d).log \
2>/dev/nullCapture the Gist URL from the output (it looks like https://gist.github.com/...).
<full log file(s) attached as GitHub Gist — see link below> placeholder in the issue body with the actual Gist URL.Note: Gists are secret (not listed publicly) but accessible to anyone with the link.
gh issue create \
--repo codemie-ai/codemie-code \
--title "<issue title>" \
--body "<issue body with gist URL inserted>" \
--label "<bug|enhancement|question>"After the issue is created, tell the user:
gh issue create output)© codemie-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in src/agents/plugins/claude/plugin/skills/report-issue of codemie-ai/codemie-code.
Open the folder on GitHubat commit 0218c8d
Report Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Report Issue this skillcodemie-ai/codemie-code | 294 | — | ~2.3k | Automated safety check: Notes | Apache-2.0 | |
| DeerFlow Smoke Testbytedance/deer-flow | 83k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness | 1.7k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Evidence-Driven Testingmichaelshimeles/skills | 1.3k | 1 repos | ~3.9k | Automated safety check: Pass | None | |
| Senior QAnicepkg/auto-company | 192 | 3 repos | ~1.1k | Automated safety check: Notes | None | |
| Create GitHub IssueNVIDIA/OpenShell | 15k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
AMAP-ML/LongHorizon-Harness
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.
michaelshimeles/skills
Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.
nicepkg/auto-company
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications.
NVIDIA/OpenShell
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.
ClickHouse/clickhouse-java
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
codemie-ai/codemie-code
CodeMie Analytics expert — use this skill whenever the user asks about CodeMie usage data, AI adoption metrics, user leaderboards, CLI insights, spending, LiteLLM costs, token usage, or wants to…
codemie-ai/codemie-code
Build static HTML pages, reports, dashboards, and mockups that match the CodeMie UI design system.
codemie-ai/codemie-code
Work with Microsoft 365 services via the Graph API — emails, calendar events, SharePoint sites (read and write), Teams chats and channel messages, OneDrive files, OneNote notebooks, Planner task…
codemie-ai/codemie-code
Build, test and autonomously improve CodeMie platform assistants.
codemie-ai/codemie-code
Release a new version of CodeMie CLI. An agent skill from codemie-ai/codemie-code.
codemie-ai/codemie-code
Business Analyst Assistant - expert to work with Jira. An agent skill from codemie-ai/codemie-code.
Categories
This skill should be used when the user wants to report a bug, file an issue, or suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub). Report Issue is an agent skill from codemie-ai/codemie-code. This skill should be used when the user wants to report a bug, file an issue, or suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub).
Report Issue fits situations like: wants to report a bug; suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub); phrases include: report a bug; submit an issue.
Run `npx skills add codemie-ai/codemie-code --skill report-issue -a claude-code`. Or copy the skill folder (src/agents/plugins/claude/plugin/skills/report-issue in codemie-ai/codemie-code) into .claude/skills/report-issue in your project. Claude Code loads it when a task matches its description.
Run `npx skills add codemie-ai/codemie-code --skill report-issue -a codex`. Or copy the skill folder (src/agents/plugins/claude/plugin/skills/report-issue in codemie-ai/codemie-code) into .agents/skills/report-issue in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codemie-ai/codemie-code --skill report-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/report-issue, .gemini/skills/report-issue, .github/skills/report-issue and .opencode/skills/report-issue in your project.
Going by SKILL.md and its folder, Report Issue needs the command-line tools its instructions call (gh, node, npm, brew, apt and dnf). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash, Read, Grep.
SKILL.md names 2 domains. In commands or code: gist.github.com; the agent is likely to contact it when it follows the instructions. As links in the text: cli.github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (runs commands with sudo; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Report Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Report Issue: DeerFlow Smoke Test (bytedance/deer-flow, 83k stars), Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars) and Senior QA (nicepkg/auto-company, 192 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
codemie-ai (a GitHub user) maintains it in codemie-ai/codemie-code, which has 294 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: codemie-ai/codemie-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.