본문으로 건너뛰기
cccskills
무료GitHub에 공개

dashboard-domain-specification

Create a detailed specification for a dashboard, covering its purpose, panels, data sources, refresh schedules, and interactions. Use a reusable structure to document what each panel shows and how users and external systems interact with it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

A reusable template for defining detailed domain specifications for dashboard projects, including panel requirements, data sources, and interfaces.

설치 방법 보기

이럴 때 유용합니다

  • Define requirements before building a dashboard
  • Document data sources and refresh schedules for each panel
  • Specify navigation and external system connections
  • Standardize specifications across dashboard projects

포함된 파일(2)

  • SKILL.md2.3 KB
  • .skill_id44 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Dashboard Domain Specification

This skill provides a structured approach to creating detailed domain specifications for dashboard projects. It ensures clarity and completeness by covering panel requirements, data sources, and interfaces.

Steps

  1. Define Dashboard Purpose:

    • Clearly state the primary goal of the dashboard (e.g., monitoring, analytics, reporting).
  2. List Panels:

    • Enumerate all panels to be included in the dashboard.
    • For each panel, specify:
      • Title: Descriptive name of the panel.
      • Purpose: What the panel aims to display or achieve.
      • Data Sources: Where the data for the panel will come from (e.g., APIs, databases).
      • Refresh Rate: How often the data should be updated (e.g., real-time, hourly).
  3. Specify Data Sources:

    • Detail each data source, including:
      • Type: API, database, file, etc.
      • Endpoint/Path: URL or path to access the data.
      • Authentication: Any required credentials or tokens.
      • Data Format: JSON, CSV, etc.
  4. Define Interfaces:

    • Describe the interfaces for interacting with the dashboard:
      • User Interface: Layout, navigation, and interactivity.
      • Programmatic Interface: APIs or hooks for external systems.
  5. Include Examples:

    • Provide sample configurations or code snippets for common panels (e.g., time-series charts, tables).

Example

Panel Specification

- title: "Daily Active Users"
  purpose: "Display the number of active users per day"
  data_sources:
    - type: "API"
      endpoint: "https://api.example.com/users/daily"
      authentication: "Bearer token"
      data_format: "JSON"
  refresh_rate: "hourly"

Data Source Specification

- name: "User Activity API"
  type: "REST API"
  endpoint: "https://api.example.com/users"
  authentication: "OAuth 2.0"
  data_format: "JSON"

Best Practices

  • Modularity: Keep panel specifications modular for easy updates.
  • Consistency: Use consistent naming conventions for panels and data sources.
  • Documentation: Maintain detailed documentation for all components

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8천2026년 8월 13일 업데이트

HKUDS의 스킬 모두 보기

이 스킬의 문제 신고