메뉴
Use when creating, validating, serving, or documenting Hasna agent-managed project dashboards and JSON Render reports with the Projects CLI, provider panels, .hasna/project layout, or
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Merge a GitHub pull request, merge when green, use a merge queue, or decide whether a pull request is mergeable. Use only for explicit merge intent, not ordinary review.
Run hosted browser automation and page extraction through the Skills runtime.
Run hosted deep research with parallel search, synthesis, citations, source notes, and downloadable report artifacts.
Generate images using OpenAI, Minimax, or Gemini through the hosted Skills runtime with provider-cost pricing.
Create and manage grouped tmux sessions where each session focuses on its own window and its own folder. Knows workspace layout, naming conventions, and both multi-project and multi-agent patterns.
Transcribe audio, video, YouTube, Vimeo, and generic media URLs with iapp-transcriber or the hosted Skills runtime. Supports OpenAI GPT-4o transcription, OpenAI diarization, ElevenLabs Scribe v2, DeepGram, chunking, source metadata, subtitles, and JSON outputs.
| name | project-dashboard-reports |
| description | Use when creating, validating, serving, or documenting Hasna agent-managed project dashboards and JSON Render reports with the Projects CLI, provider panels, .hasna/project layout, or |
Use the Projects-owned dashboard surface for agent-managed project folders.
Do not build a one-off app or chat UI unless open-projects cannot express the
surface.
Workspace/<division>/project/<project-slug>.hasna/project/.hasna/project/dashboard/render.json.hasna/project/dashboard/snapshots/latest.snapshot.jsoniproj-<project-slug>, human display
#iproj-<project-slug>Project folders may contain private documents. Dashboard JSON should use ids, counts, statuses, resource refs, evidence refs, and redacted summaries rather than raw emails, contract clauses, account numbers, identity documents, or credentials.
Use the explicit dashboard namespace:
projects dashboard snapshot <project> --write --json
projects dashboard render <project> --json
projects dashboard validate <project> --json
PROJECTS_DASHBOARD_TOKEN=<token> projects dashboard serve <project> --host 0.0.0.0 --port <port>
snapshot, render, and validate are read-only unless --write is passed.
For non-loopback serving, use --token, PROJECTS_DASHBOARD_TOKEN, or an
explicit --trust-network choice. Do not put dashboard access tokens in URLs,
tasks, reports, render specs, or chat messages.
Provider CLIs should emit bounded hasna.project_panel.v1 JSON:
todos project-panel --project <project> --json --contract
files project-panel --project <project> --json --contract
mailery project-panel --project <project> --limit 20 --json --contract
conversations project-panel --project <project> --limit 30 --json --contract
knowledge project-panel --project <project> --scope project --limit 30 --json --contract
mementos --json project-panel --project <project> --contract
reports project-panel --project <project> --json --contract
Run provider commands from the project cwd when project-local stores matter. Mailery remains workspace-scoped until explicit project-email mapping exists. Providers should degrade to unavailable/error panels instead of dumping raw content.
todos; use messages only for coordination.projects dashboard validate <project> --json passes.open-projects.