Agent skill
happiness-dashboard
Evidence framework data dashboard with DuckDB. Write SQL in markdown to create visualizations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/happiness-dashboard
SKILL.md
Happiness Dashboard
An interactive data dashboard using Evidence framework - write SQL queries in markdown to create visualizations.
Tech Stack
- Framework: Evidence
- Database: DuckDB (embedded)
- Frontend: Svelte
- Package Manager: pnpm
- Output:
builddirectory - Dev Port: 3000
Setup
1. Clone the Template
git clone --depth 1 https://github.com/Eng0AI/happiness-dashboard-template.git .
If the directory is not empty:
git clone --depth 1 https://github.com/Eng0AI/happiness-dashboard-template.git _temp_template
mv _temp_template/* _temp_template/.* . 2>/dev/null || true
rm -rf _temp_template
2. Remove Git History (Optional)
rm -rf .git
git init
3. Install Dependencies
pnpm install
4. Process Data Sources
pnpm run sources
Build
pnpm run build
Generates static site in build/ directory.
Deploy
Vercel (Recommended)
vercel pull --yes -t $VERCEL_TOKEN
vercel build --prod -t $VERCEL_TOKEN
vercel deploy --prebuilt --prod --yes -t $VERCEL_TOKEN
Important: Deploy from project root, not build/ directory.
Netlify
netlify deploy --prod --dir=build
Data Sources
CSV files in sources/happiness_score/:
hs2024.csv- Current year happiness datahsArchive.csv- Historical happiness data
Notes
- Use pnpm (not npm) -
.npmrchasshamefully-hoist=truefor Evidence compatibility - Build locally - Vercel/Netlify build can timeout due to DuckDB compilation (40+ min)
- Uses CSV files, no database setup needed
- Never run
pnpm run devin VM environment
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?