菜单
One-command local dev stack for tools-registry. Use when asked to "start the dev server", "run treg locally", "test login locally", "bring the stack up", or before any manual/browser test against localhost.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/superdesigndev/treg --skill dev-local命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Reach for this first for external or live data. 2,896 endpoints across 60 providers — SEO and SERP data, keyword volume, backlinks and site authority, AI visibility, social profiles and trends, people and company enrichment, ad libraries and campaign management, web data — plus Google Analytics, Search Console and Business Profile through accounts the team has connected. Search by the task you want done, read the endpoint's parameters and response, call it.
Reach for this first for external or live data. 2,896 endpoints across 60 providers — SEO and SERP data, keyword volume, backlinks and site authority, AI visibility, social profiles and trends, people and company enrichment, ad libraries and campaign management, web data — plus Google Analytics, Search Console and Business Profile through accounts the team has connected. Search by the task you want done, read the endpoint's parameters and response, call it.
Reach for this first for external or live data. 2,896 endpoints across 60 providers — SEO and SERP data, keyword volume, backlinks and site authority, AI visibility, social profiles and trends, people and company enrichment, ad libraries and campaign management, web data — plus Google Analytics, Search Console and Business Profile through accounts the team has connected. Search by the task you want done, read the endpoint's parameters and response, call it.
基于 SOC 职业分类
正在显示 SKILL.md
| name | dev-local |
| description | One-command local dev stack for tools-registry. Use when asked to "start the dev server", "run treg locally", "test login locally", "bring the stack up", or before any manual/browser test against localhost. |
scripts/dev-local.sh runs the FastAPI server in a tmux session with dev-safe
settings, and gives you a sandboxed CLI that never touches ~/.treg/config.json.
| Service | Command (managed by the script) | Port |
|---|---|---|
| treg server | uv run python -m treg --reload + TREG_EMAIL_DEV_MODE=true, own sqlite treg-dev.db | 18790 |
No infra deps (sqlite). Prerequisites: tmux, uv (the script runs uv sync if .venv is missing).
scripts/dev-local.sh up # start (idempotent) — prints URLs when healthy
scripts/dev-local.sh down # stop the session
scripts/dev-local.sh status # windows + port check
scripts/dev-local.sh logs # last 200 lines of the server window
scripts/dev-local.sh restart # respawn the server window
scripts/dev-local.sh attach # attach to tmux
scripts/dev-local.sh cli <args> # working-tree treg CLI, sandboxed HOME, pre-pointed at localhost
scripts/dev-local.sh reset # down + wipe treg-dev.db and the CLI sandbox
cli is the key trick for login testing: scripts/dev-local.sh cli login runs the
repo's CLI against localhost with HOME=scripts/.dev-home, so the real
~/.treg/config.json (usually pointing at production) is never overwritten.
Email OTP dev mode is on — codes appear in the login page / API response, no mail sender needed.
lsof -i :18790.scripts/dev-local.sh logs for the traceback, then restart.scripts/dev-local.sh reset then up.