/ar:ar-status — Experiment Dashboard
Show experiment dashboard with results, active loops, and progress.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/ar-status, including the files SKILL.md points to. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/engineering/autoresearch-agent/skills/ar-status#main ~/.claude/skills/ar-statusFor one project only, change the path to .claude/skills/ar-status. This skill also uses loop.json — copying SKILL.md alone won't be enough. See the folder on GitHub.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of /ar:ar-status — Experiment Dashboard
Show the full text72 lines
| name | description | command |
|---|---|---|
| ar-status | Show experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going. | /ar:ar-status |
/ar:ar-status — Experiment Dashboard
Show experiment results, active loops, and progress across all experiments.
Usage
/ar:ar-status # Full dashboard
/ar:ar-status engineering/api-speed # Single experiment detail
/ar:ar-status --domain engineering # All experiments in a domain
/ar:ar-status --format markdown # Export as markdown
/ar:ar-status --format csv --output results.csv # Export as CSV
What It Does
Single experiment
python {skill_path}/scripts/log_results.py --experiment {domain}/{name}
Also check for active loop:
cat .autoresearch/{domain}/{name}/loop.json 2>/dev/null
If loop.json exists, show:
Active loop: every {interval} (cron ID: {id}, started: {date})
Domain view
python {skill_path}/scripts/log_results.py --domain {domain}
Full dashboard
python {skill_path}/scripts/log_results.py --dashboard
For each experiment, also check for loop.json and show loop status.
Export
# CSV
python {skill_path}/scripts/log_results.py --dashboard --format csv --output {file}
# Markdown
python {skill_path}/scripts/log_results.py --dashboard --format markdown --output {file}
Output Example
DOMAIN EXPERIMENT RUNS KEPT BEST CHANGE STATUS LOOP
engineering api-speed 47 14 185ms -76.9% active every 1h
engineering bundle-size 23 8 412KB -58.3% paused —
marketing medium-ctr 31 11 8.4/10 +68.0% active daily
prompts support-tone 15 6 82/100 +46.4% done —
| 1 | |
| 2 | name "ar-status" |
| 3 | description "Show experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going." |
| 4 | command /ar:ar-status |
| 5 | |
| 6 | |
| 7 | # /ar:ar-status — Experiment Dashboard |
| 8 | |
| 9 | Show experiment results, active loops, and progress across all experiments. |
| 10 | |
| 11 | ## Usage |
| 12 | |
| 13 | |
| 14 | /ar:ar-status # Full dashboard |
| 15 | /ar:ar-status engineering/api-speed # Single experiment detail |
| 16 | /ar:ar-status --domain engineering # All experiments in a domain |
| 17 | /ar:ar-status --format markdown # Export as markdown |
| 18 | /ar:ar-status --format csv --output results.csv # Export as CSV |
| 19 | |
| 20 | |
| 21 | ## What It Does |
| 22 | |
| 23 | ### Single experiment |
| 24 | |
| 25 | |
| 26 | python {skill_path}/scripts/log_results.py --experiment {domain}/{name} |
| 27 | |
| 28 | |
| 29 | Also check for active loop: |
| 30 | |
| 31 | cat .autoresearch/{domain}/{name}/loop.json 2>/dev/null |
| 32 | |
| 33 | |
| 34 | If loop.json exists, show: |
| 35 | |
| 36 | Active loop: every {interval} (cron ID: {id}, started: {date}) |
| 37 | |
| 38 | |
| 39 | ### Domain view |
| 40 | |
| 41 | |
| 42 | python {skill_path}/scripts/log_results.py --domain {domain} |
| 43 | |
| 44 | |
| 45 | ### Full dashboard |
| 46 | |
| 47 | |
| 48 | python {skill_path}/scripts/log_results.py --dashboard |
| 49 | |
| 50 | |
| 51 | For each experiment, also check for loop.json and show loop status. |
| 52 | |
| 53 | ### Export |
| 54 | |
| 55 | |
| 56 | # CSV |
| 57 | python {skill_path}/scripts/log_results.py --dashboard --format csv --output {file} |
| 58 | |
| 59 | # Markdown |
| 60 | python {skill_path}/scripts/log_results.py --dashboard --format markdown --output {file} |
| 61 | |
| 62 | |
| 63 | ## Output Example |
| 64 | |
| 65 | |
| 66 | DOMAIN EXPERIMENT RUNS KEPT BEST CHANGE STATUS LOOP |
| 67 | engineering api-speed 47 14 185ms -76.9% active every 1h |
| 68 | engineering bundle-size 23 8 412KB -58.3% paused — |
| 69 | marketing medium-ctr 31 11 8.4/10 +68.0% active daily |
| 70 | prompts support-tone 15 6 82/100 +46.4% done — |
| 71 | |
| 72 |
Discussion
Analytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Earnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly.Path A — List-styleSave the results of an in-chat data-exploration session as a TL report. Triggers when the user wants to persist a channels / brands / videos (uploads) / sponsorships list or filtered set they've been working with — phrases like "save this as a report", "save the list", "turn this into a campaign", "persist this", "make a report from what you found", "save the result", "I want to come back to this".Investment tracking dashboardCreate a user-friendly dashboard to track and manage your investments effectively.
Browse more free Claude skills or everything in Data & analytics.