@hybridlabor-api/bdb-antigravity-skills 1.0.0

package/skills/global_legacy/nextjs-best-practices/SKILL.md

@@ -0,0 +1,213 @@
+---
+name: nextjs-best-practices
+description: "Next.js App Router principles. Server Components, data fetching, routing patterns."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Next.js Best Practices
+
+> Principles for Next.js App Router development.
+
+---
+
+## 1. Server vs Client Components
+
+### Decision Tree
+
+```
+Does it need...?
+│
+├── useState, useEffect, event handlers
+│   └── Client Component ('use client')
+│
+├── Direct data fetching, no interactivity
+│   └── Server Component (default)
+│
+└── Both? 
+    └── Split: Server parent + Client child
+```
+
+### By Default
+
+| Type | Use |
+|------|-----|
+| **Server** | Data fetching, layout, static content |
+| **Client** | Forms, buttons, interactive UI |
+
+---
+
+## 2. Data Fetching Patterns
+
+### Fetch Strategy
+
+| Pattern | Use |
+|---------|-----|
+| **Default** | Static (cached at build) |
+| **Revalidate** | ISR (time-based refresh) |
+| **No-store** | Dynamic (every request) |
+
+### Data Flow
+
+| Source | Pattern |
+|--------|---------|
+| Database | Server Component fetch |
+| API | fetch with caching |
+| User input | Client state + server action |
+
+---
+
+## 3. Routing Principles
+
+### File Conventions
+
+| File | Purpose |
+|------|---------|
+| `page.tsx` | Route UI |
+| `layout.tsx` | Shared layout |
+| `loading.tsx` | Loading state |
+| `error.tsx` | Error boundary |
+| `not-found.tsx` | 404 page |
+
+### Route Organization
+
+| Pattern | Use |
+|---------|-----|
+| Route groups `(name)` | Organize without URL |
+| Parallel routes `@slot` | Multiple same-level pages |
+| Intercepting `(.)` | Modal overlays |
+
+---
+
+## 4. API Routes
+
+### Route Handlers
+
+| Method | Use |
+|--------|-----|
+| GET | Read data |
+| POST | Create data |
+| PUT/PATCH | Update data |
+| DELETE | Remove data |
+
+### Best Practices
+
+- Validate input with Zod
+- Return proper status codes
+- Handle errors gracefully
+- Use Edge runtime when possible
+
+---
+
+## 5. Performance Principles
+
+### Image Optimization
+
+- Use next/image component
+- Set priority for above-fold
+- Provide blur placeholder
+- Use responsive sizes
+
+### Bundle Optimization
+
+- Dynamic imports for heavy components
+- Route-based code splitting (automatic)
+- Analyze with bundle analyzer
+
+---
+
+## 6. Metadata
+
+### Static vs Dynamic
+
+| Type | Use |
+|------|-----|
+| Static export | Fixed metadata |
+| generateMetadata | Dynamic per-route |
+
+### Essential Tags
+
+- title (50-60 chars)
+- description (150-160 chars)
+- Open Graph images
+- Canonical URL
+
+---
+
+## 7. Caching Strategy
+
+### Cache Layers
+
+| Layer | Control |
+|-------|---------|
+| Request | fetch options |
+| Data | revalidate/tags |
+| Full route | route config |
+
+### Revalidation
+
+| Method | Use |
+|--------|-----|
+| Time-based | `revalidate: 60` |
+| On-demand | `revalidatePath/Tag` |
+| No cache | `no-store` |
+
+---
+
+## 8. Server Actions
+
+### Use Cases
+
+- Form submissions
+- Data mutations
+- Revalidation triggers
+
+### Best Practices
+
+- Mark with 'use server'
+- Validate all inputs
+- Return typed responses
+- Handle errors
+
+---
+
+## 9. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| 'use client' everywhere | Server by default |
+| Fetch in client components | Fetch in server |
+| Skip loading states | Use loading.tsx |
+| Ignore error boundaries | Use error.tsx |
+| Large client bundles | Dynamic imports |
+
+---
+
+## 10. Project Structure
+
+```
+app/
+├── (marketing)/     # Route group
+│   └── page.tsx
+├── (dashboard)/
+│   ├── layout.tsx   # Dashboard layout
+│   └── page.tsx
+├── api/
+│   └── [resource]/
+│       └── route.ts
+└── components/
+    └── ui/
+```
+
+---
+
+> **Remember:** Server Components are the default for a reason. Start there, add client only when needed.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
+
+## Limitations
+- Use this skill only when the task clearly matches the scope described above.
+- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

package/skills/global_legacy/notion-automation/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: notion-automation
+description: "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas."
+risk: critical
+source: community
+date_added: "2026-02-27"
+---
+
+# Notion Automation via Rube MCP
+
+Automate Notion operations through Composio's Notion toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Notion connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `notion`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `notion`
+3. If connection is not ACTIVE, follow the returned auth link to complete Notion OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Pages
+
+**When to use**: User wants to create, update, or archive Notion pages
+
+**Tool sequence**:
+1. `NOTION_SEARCH_NOTION_PAGE` - Find parent page or existing page [Prerequisite]
+2. `NOTION_CREATE_NOTION_PAGE` - Create a new page under a parent [Optional]
+3. `NOTION_RETRIEVE_PAGE` - Get page metadata/properties [Optional]
+4. `NOTION_UPDATE_PAGE` - Update page properties, title, icon, cover [Optional]
+5. `NOTION_ARCHIVE_NOTION_PAGE` - Soft-delete (archive) a page [Optional]
+
+**Key parameters**:
+- `query`: Search text for SEARCH_NOTION_PAGE
+- `parent_id`: Parent page or database ID
+- `page_id`: Page ID for retrieval/update/archive
+- `properties`: Page property values matching parent schema
+
+**Pitfalls**:
+- RETRIEVE_PAGE returns only metadata/properties, NOT body content; use FETCH_BLOCK_CONTENTS for page body
+- ARCHIVE_NOTION_PAGE is a soft-delete (sets archived=true), not permanent deletion
+- Broad searches can look incomplete unless has_more/next_cursor is fully paginated
+
+### 2. Query and Manage Databases
+
+**When to use**: User wants to query database rows, insert entries, or update records
+
+**Tool sequence**:
+1. `NOTION_SEARCH_NOTION_PAGE` - Find the database by name [Prerequisite]
+2. `NOTION_FETCH_DATABASE` - Inspect schema and properties [Prerequisite]
+3. `NOTION_QUERY_DATABASE` / `NOTION_QUERY_DATABASE_WITH_FILTER` - Query rows [Required]
+4. `NOTION_INSERT_ROW_DATABASE` - Add new entries [Optional]
+5. `NOTION_UPDATE_ROW_DATABASE` - Update existing entries [Optional]
+
+**Key parameters**:
+- `database_id`: Database ID (from search or URL)
+- `filter`: Filter object matching Notion filter syntax
+- `sorts`: Array of sort objects
+- `start_cursor`: Pagination cursor from previous response
+- `properties`: Property values matching database schema for inserts/updates
+
+**Pitfalls**:
+- 404 object_not_found usually means wrong database_id or the database is not shared with the integration
+- Results are paginated; ignoring has_more/next_cursor silently truncates reads
+- Schema mismatches or missing required properties cause 400 validation_error
+- Formula and read-only fields cannot be set via INSERT_ROW_DATABASE
+- Property names in filters must match schema exactly (case-sensitive)
+
+### 3. Manage Blocks and Page Content
+
+**When to use**: User wants to read, append, or modify content blocks in a page
+
+**Tool sequence**:
+1. `NOTION_FETCH_BLOCK_CONTENTS` - Read child blocks of a page [Required]
+2. `NOTION_ADD_MULTIPLE_PAGE_CONTENT` - Append blocks to a page [Optional]
+3. `NOTION_APPEND_TEXT_BLOCKS` - Append text-only blocks [Optional]
+4. `NOTION_REPLACE_PAGE_CONTENT` - Replace all page content [Optional]
+5. `NOTION_DELETE_BLOCK` - Remove a specific block [Optional]
+
+**Key parameters**:
+- `block_id` / `page_id`: Target page or block ID
+- `content_blocks`: Array of block objects (NOT child_blocks)
+- `text`: Plain text content for APPEND_TEXT_BLOCKS
+
+**Pitfalls**:
+- Use `content_blocks` parameter, NOT `child_blocks` -- the latter fails validation
+- ADD_MULTIPLE_PAGE_CONTENT fails on archived pages; unarchive via UPDATE_PAGE first
+- Created blocks are in response.data.results; persist block IDs for later edits
+- DELETE_BLOCK is archival (archived=true), not permanent deletion
+
+### 4. Manage Database Schema
+
+**When to use**: User wants to create databases or modify their structure
+
+**Tool sequence**:
+1. `NOTION_FETCH_DATABASE` - Inspect current schema [Prerequisite]
+2. `NOTION_CREATE_DATABASE` - Create a new database [Optional]
+3. `NOTION_UPDATE_SCHEMA_DATABASE` - Modify database properties [Optional]
+
+**Key parameters**:
+- `parent_id`: Parent page ID for new databases
+- `title`: Database title
+- `properties`: Property definitions with types and options
+- `database_id`: Database ID for schema updates
+
+**Pitfalls**:
+- Cannot change property types via UPDATE_SCHEMA; must create new property and migrate data
+- Formula, rollup, and relation properties have complex configuration requirements
+
+### 5. Manage Users and Comments
+
+**When to use**: User wants to list workspace users or manage comments on pages
+
+**Tool sequence**:
+1. `NOTION_LIST_USERS` - List all workspace users [Optional]
+2. `NOTION_GET_ABOUT_ME` - Get current authenticated user [Optional]
+3. `NOTION_CREATE_COMMENT` - Add a comment to a page [Optional]
+4. `NOTION_FETCH_COMMENTS` - List comments on a page [Optional]
+
+**Key parameters**:
+- `page_id`: Page ID for comments (also called `discussion_id`)
+- `rich_text`: Comment content as rich text array
+
+**Pitfalls**:
+- Comments are linked to pages, not individual blocks
+- User IDs from LIST_USERS are needed for people-type property filters
+
+## Common Patterns
+
+### ID Resolution
+
+**Page/Database name -> ID**:
+```
+1. Call NOTION_SEARCH_NOTION_PAGE with query=name
+2. Paginate with has_more/next_cursor until found
+3. Extract id from matching result
+```
+
+**Database schema inspection**:
+```
+1. Call NOTION_FETCH_DATABASE with database_id
+2. Extract properties object for field names and types
+3. Use exact property names in queries and inserts
+```
+
+### Pagination
+
+- Set `page_size` for results per page (max 100)
+- Check response for `has_more` boolean
+- Pass `start_cursor` or `next_cursor` in next request
+- Continue until `has_more` is false
+
+### Notion Filter Syntax
+
+**Single filter**:
+```json
+{"property": "Status", "select": {"equals": "Done"}}
+```
+
+**Compound filter**:
+```json
+{"and": [
+  {"property": "Status", "select": {"equals": "In Progress"}},
+  {"property": "Assignee", "people": {"contains": "user-id"}}
+]}
+```
+
+## Known Pitfalls
+
+**Integration Sharing**:
+- Pages and databases must be shared with the Notion integration to be accessible
+- Title queries can return 0 when the item is not shared with the integration
+
+**Property Types**:
+- Property names are case-sensitive and must match schema exactly
+- Formula, rollup, and created_time fields are read-only
+- Select/multi-select values must match existing options unless creating new ones
+
+**Response Parsing**:
+- Response data may be nested under `data_preview` or `data.results`
+- Parse defensively with fallbacks for different nesting levels
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search pages/databases | NOTION_SEARCH_NOTION_PAGE | query |
+| Create page | NOTION_CREATE_NOTION_PAGE | parent_id, properties |
+| Get page metadata | NOTION_RETRIEVE_PAGE | page_id |
+| Update page | NOTION_UPDATE_PAGE | page_id, properties |
+| Archive page | NOTION_ARCHIVE_NOTION_PAGE | page_id |
+| Duplicate page | NOTION_DUPLICATE_PAGE | page_id |
+| Get page blocks | NOTION_FETCH_BLOCK_CONTENTS | block_id |
+| Append blocks | NOTION_ADD_MULTIPLE_PAGE_CONTENT | page_id, content_blocks |
+| Append text | NOTION_APPEND_TEXT_BLOCKS | page_id, text |
+| Replace content | NOTION_REPLACE_PAGE_CONTENT | page_id, content_blocks |
+| Delete block | NOTION_DELETE_BLOCK | block_id |
+| Query database | NOTION_QUERY_DATABASE | database_id, filter, sorts |
+| Query with filter | NOTION_QUERY_DATABASE_WITH_FILTER | database_id, filter |
+| Insert row | NOTION_INSERT_ROW_DATABASE | database_id, properties |
+| Update row | NOTION_UPDATE_ROW_DATABASE | page_id, properties |
+| Get database schema | NOTION_FETCH_DATABASE | database_id |
+| Create database | NOTION_CREATE_DATABASE | parent_id, title, properties |
+| Update schema | NOTION_UPDATE_SCHEMA_DATABASE | database_id, properties |
+| List users | NOTION_LIST_USERS | (none) |
+| Create comment | NOTION_CREATE_COMMENT | page_id, rich_text |
+| List comments | NOTION_FETCH_COMMENTS | page_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
+
+## Limitations
+- Use this skill only when the task clearly matches the scope described above.
+- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

package/skills/global_legacy/obsidian-markdown/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: obsidian-markdown
+description: Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
+risk: unknown
+source: "https://github.com/kepano/obsidian-skills"
+date_added: "2026-03-21"
+---
+
+# Obsidian Flavored Markdown Skill
+
+Create and edit valid Obsidian Flavored Markdown. Obsidian extends CommonMark and GFM with wikilinks, embeds, callouts, properties, comments, and other syntax. This skill covers only Obsidian-specific extensions -- standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.
+
+## When to Use
+- Use when writing or editing Markdown notes intended for Obsidian.
+- Use when the task involves wikilinks, embeds, callouts, frontmatter properties, or Obsidian-specific syntax.
+- Use when the user wants notes that render correctly inside an Obsidian vault.
+
+## Workflow: Creating an Obsidian Note
+
+1. **Add frontmatter** with properties (title, tags, aliases) at the top of the file. See [PROPERTIES.md](references/PROPERTIES.md) for all property types.
+2. **Write content** using standard Markdown for structure, plus Obsidian-specific syntax below.
+3. **Link related notes** using wikilinks (`[[Note]]`) for internal vault connections, or standard Markdown links for external URLs.
+4. **Embed content** from other notes, images, or PDFs using the `![[embed]]` syntax. See [EMBEDS.md](references/EMBEDS.md) for all embed types.
+5. **Add callouts** for highlighted information using `> [!type]` syntax. See [CALLOUTS.md](references/CALLOUTS.md) for all callout types.
+6. **Verify** the note renders correctly in Obsidian's reading view.
+
+> When choosing between wikilinks and Markdown links: use `[[wikilinks]]` for notes within the vault (Obsidian tracks renames automatically) and plain Markdown links for external URLs only.
+
+## Internal Links (Wikilinks)
+
+```markdown
+[[Note Name]]                          Link to note
+[[Note Name|Display Text]]             Custom display text
+[[Note Name#Heading]]                  Link to heading
+[[Note Name#^block-id]]                Link to block
+[[#Heading in same note]]              Same-note heading link
+```
+
+Define a block ID by appending `^block-id` to any paragraph:
+
+```markdown
+This paragraph can be linked to. ^my-block-id
+```
+
+For lists and quotes, place the block ID on a separate line after the block:
+
+```markdown
+> A quote block
+
+^quote-id
+```
+
+## Embeds
+
+Prefix any wikilink with `!` to embed its content inline:
+
+```markdown
+![[Note Name]]                         Embed full note
+![[Note Name#Heading]]                 Embed section
+![[image.png]]                         Embed image
+![[image.png|300]]                     Embed image with width
+![[document.pdf#page=3]]               Embed PDF page
+```
+
+See [EMBEDS.md](references/EMBEDS.md) for audio, video, search embeds, and external images.
+
+## Callouts
+
+```markdown
+> [!note]
+> Basic callout.
+
+> [!warning] Custom Title
+> Callout with a custom title.
+
+> [!faq]- Collapsed by default
+> Foldable callout (- collapsed, + expanded).
+```
+
+Common types: `note`, `tip`, `warning`, `info`, `example`, `quote`, `bug`, `danger`, `success`, `failure`, `question`, `abstract`, `todo`.
+
+See [CALLOUTS.md](references/CALLOUTS.md) for the full list with aliases, nesting, and custom CSS callouts.
+
+## Properties (Frontmatter)
+
+```yaml
+---
+title: My Note
+date: 2024-01-15
+tags:
+  - project
+  - active
+aliases:
+  - Alternative Name
+cssclasses:
+  - custom-class
+---
+```
+
+Default properties: `tags` (searchable labels), `aliases` (alternative note names for link suggestions), `cssclasses` (CSS classes for styling).
+
+See [PROPERTIES.md](references/PROPERTIES.md) for all property types, tag syntax rules, and advanced usage.
+
+## Tags
+
+```markdown
+#tag                    Inline tag
+#nested/tag             Nested tag with hierarchy
+```
+
+Tags can contain letters, numbers (not first character), underscores, hyphens, and forward slashes. Tags can also be defined in frontmatter under the `tags` property.
+
+## Comments
+
+```markdown
+This is visible %%but this is hidden%% text.
+
+%%
+This entire block is hidden in reading view.
+%%
+```
+
+## Obsidian-Specific Formatting
+
+```markdown
+==Highlighted text==                   Highlight syntax
+```
+
+## Math (LaTeX)
+
+```markdown
+Inline: $e^{i\pi} + 1 = 0$
+
+Block:
+$$
+\frac{a}{b} = c
+$$
+```
+
+## Diagrams (Mermaid)
+
+````markdown
+```mermaid
+graph TD
+    A[Start] --> B{Decision}
+    B -->|Yes| C[Do this]
+    B -->|No| D[Do that]
+```
+````
+
+To link Mermaid nodes to Obsidian notes, add `class NodeName internal-link;`.
+
+## Footnotes
+
+```markdown
+Text with a footnote[^1].
+
+[^1]: Footnote content.
+
+Inline footnote.^[This is inline.]
+```
+
+## Complete Example
+
+````markdown
+---
+title: Project Alpha
+date: 2024-01-15
+tags:
+  - project
+  - active
+status: in-progress
+---
+
+# Project Alpha
+
+This project aims to [[improve workflow]] using modern techniques.
+
+> [!important] Key Deadline
+> The first milestone is due on ==January 30th==.
+
+## Tasks
+
+- [x] Initial planning
+- [ ] Development phase
+  - [ ] Backend implementation
+  - [ ] Frontend design
+
+## Notes
+
+The algorithm uses $O(n \log n)$ sorting. See [[Algorithm Notes#Sorting]] for details.
+
+![[Architecture Diagram.png|600]]
+
+Reviewed in [[Meeting Notes 2024-01-10#Decisions]].
+````
+
+## References
+
+- [Obsidian Flavored Markdown](https://help.obsidian.md/obsidian-flavored-markdown)
+- [Internal links](https://help.obsidian.md/links)
+- [Embed files](https://help.obsidian.md/embeds)
+- [Callouts](https://help.obsidian.md/callouts)
+- [Properties](https://help.obsidian.md/properties)
+
+## Limitations
+- Use this skill only when the task clearly matches the scope described above.
+- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

package/skills/global_legacy/obsidian-markdown/references/CALLOUTS.md

@@ -0,0 +1,58 @@
+# Callouts Reference
+
+## Basic Callout
+
+```markdown
+> [!note]
+> This is a note callout.
+
+> [!info] Custom Title
+> This callout has a custom title.
+
+> [!tip] Title Only
+```
+
+## Foldable Callouts
+
+```markdown
+> [!faq]- Collapsed by default
+> This content is hidden until expanded.
+
+> [!faq]+ Expanded by default
+> This content is visible but can be collapsed.
+```
+
+## Nested Callouts
+
+```markdown
+> [!question] Outer callout
+> > [!note] Inner callout
+> > Nested content
+```
+
+## Supported Callout Types
+
+| Type | Aliases | Color / Icon |
+|------|---------|-------------|
+| `note` | - | Blue, pencil |
+| `abstract` | `summary`, `tldr` | Teal, clipboard |
+| `info` | - | Blue, info |
+| `todo` | - | Blue, checkbox |
+| `tip` | `hint`, `important` | Cyan, flame |
+| `success` | `check`, `done` | Green, checkmark |
+| `question` | `help`, `faq` | Yellow, question mark |
+| `warning` | `caution`, `attention` | Orange, warning |
+| `failure` | `fail`, `missing` | Red, X |
+| `danger` | `error` | Red, zap |
+| `bug` | - | Red, bug |
+| `example` | - | Purple, list |
+| `quote` | `cite` | Gray, quote |
+
+## Custom Callouts (CSS)
+
+```css
+.callout[data-callout="custom-type"] {
+  --callout-color: 255, 0, 0;
+  --callout-icon: lucide-alert-circle;
+}
+```