メニュー
Create and edit GemiHub Markdown notes using GFM, frontmatter, callouts, Mermaid diagrams, tables, task lists, and links.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Author and maintain GemiHub .base compatibility files for filtered table, card, and list views over workspace files.
Agent Skills: bundles of custom instructions, reference material, and workflows for the AI agent.
Create GemiHub Dashboards (.dashboard files) — a grid of widgets that embed Bases views, folder card/table/kanban views, notes, web pages, and workflow output. Use when the user asks for a dashboard, a home/overview page, or to arrange .base views and data widgets in a grid.
Create and edit GemiHub .canvas files using JSON Canvas nodes, edges, groups, colors, and file/link references.
Use when building or editing the user's webpage / website — static HTML pages, magic-link login pages, protected pages, workflow-based JSON APIs (web/api/*.yaml), publishing blog posts or announcements, wiring sheet/calendar/gmail data into pages, setting up sign-in, building contact/booking forms, or operating the admin side of an existing site. Triggering keywords include web/, gemihub.*, requireAuth, sheet-read/sheet-write, "公開する" / "サイトに追加" / "Webページ作成". Lean toward using this skill whenever the user wants to put something on their site or expose data as a JSON endpoint — even if they don't name a file under web/.
| name | markdown |
| description | Create and edit GemiHub Markdown notes using GFM, frontmatter, callouts, Mermaid diagrams, tables, task lists, and links. |
Create and edit Markdown files for GemiHub. Use this skill when working with .md or .markdown files, notes, frontmatter, callouts, Mermaid diagrams, tables, task lists, or Markdown preview behavior.
GemiHub supports standard Markdown and GitHub Flavored Markdown. Keep files portable and readable as plain text.
[label](url)) for external links.GemiHub recognizes YAML frontmatter at the top of a Markdown file.
---
title: Project Note
date: 2026-06-18
tags:
- project
- active
---
Common property types:
| Type | Example |
|---|---|
| Text | title: Project Note |
| Number | priority: 2 |
| Checkbox | done: false |
| Date | date: 2026-06-18 |
| Date and time | due: 2026-06-18T14:30:00 |
| List | tags: [project, active] or YAML list |
Use callouts for highlighted blocks in reading and preview mode.
> [!note]
> Basic callout.
> [!warning] Custom Title
> Callout with a custom title.
> [!question]- Collapsed by default
> Foldable callout. Use `-` for closed and `+` for open.
Supported types: note, abstract, info, todo, tip, success, question, warning, failure, danger, bug, example, quote.
Aliases:
| Alias | Type |
|---|---|
summary, tldr | abstract |
hint, important | tip |
check, done | success |
help, faq | question |
caution, attention | warning |
fail, missing | failure |
error | danger |
cite | quote |
GemiHub preview renders fenced Mermaid blocks.
flowchart TD
A[Start] --> B{Decision}
B -->|Yes| C[Do it]
B -->|No| D[Stop]
Keep diagrams small enough to inspect in preview. For workflows, prefer flowchart TD unless another Mermaid diagram type is clearly better.
Use valid GFM table syntax.
| Item | Owner | Status |
|------|-------|--------|
| Spec | Aki | Draft |
| Review | Mina | Pending |
- [ ] Draft outline
- [x] Confirm requirements
- [ ] Publish update
Use standard Markdown image syntax.
When adding images, use meaningful alt text and a workspace-relative path when possible.