Skip to content
cccskills
FreePublished on GitHub

gg

Work on Grida's Gateway product consumer, scoped native AI tokens, installed gg provider and Desktop integration. Use for product execution adapters, not standalone Gateway service implementation or billing policy.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Grida Gateway consumers

Grida's web, CLI and Desktop retain their authenticated native entry points. Funded product generation is delegated by the server to Grida Gateway; this repository owns the consumer adapters and product result persistence. Standalone customer API-key support is separate from the installed login-based gg provider; do not replace one credential family with the other.

Read the affected adapter in editor/lib/ai/, Platform consumers, and GRIDA-SEC-006 in SECURITY.md when touching scoped tokens. The public standalone contract is gateway.grida.ai/llms.txt.

  • Preserve authenticated organization resolution and native result DTOs.
  • Product workload credentials are server-only; never expose them to a renderer or substitute a customer's API key.
  • Keep the existing gg:ai native audience and scoped lifetime. Account tokens, scoped native tokens and product workload credentials are distinct.
  • Preserve original accepted job identity during polling, retries and asset persistence. Download failure must not resubmit paid work.
  • Do not add financial policy, another credit balance or duplicate native usage to migrated generation. Retained native consumers still use Platform admission.
  • GRIDA-GG: <surface> marks consumer/token/provider/Desktop code. It does not indicate ownership of the Gateway service or financial engine.

Use focused no-dotenv unit/API tests and editor TypeScript. The paired SDK lane requires an explicitly supplied local service fixture and synthetic credentials; ordinary tests must not load hosted keys or call paid models.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Grida AI agent system work: `@grida/daemon` (DaemonServer, loopback HTTP perimeter, files/workspaces, secrets store, daemon discovery) and `@grida/agent` (the agent tenant: sessions, providers/BYOK, runtime/tool execution, skills discovery, prompts, tiers, sandbox hosts). Use for `packages/grida-daemon/**`, `packages/grida-ai-agent/**`, desktop sidecar protocol changes, agent chat transport, and bugs in agent state or streams. For pure Electron window, preload, menu, deep-link, or CDP work, use `desktop`.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 19, 2026

Research, compare, and update shared AI model JSON for TypeScript, web, and Rust consumers. Covers text model tiers, image and video generation models, image tool models, release provenance, pricing data sourcing, and product-side catalogue cost estimates. Use when bumping model versions, adding new models, updating pricing, or auditing model specs against provider documentation.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 19, 2026

React-specific code shape in the Grida editor. Hooks cannot be tested or benchmarked and silently break tuned UX under layered composition, so they are barred from the engine and main system — load-bearing logic lives in classes and namespaces, hooks only as thin edge wires. `data-testid` follows component-root discipline: one per significant component, not scattered. Use when authoring React in `editor/grida-canvas-react/`, `editor/components/`, `editor/scaffolds/`, or `editor/app/*`.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 19, 2026

TypeScript code shape inside a well-named module — taste, not lint. Prefer one class or namespace per file (the unit a test targets) over scattered free exports; consolidate related code, don't fragment. The unit of code should be the unit of spec. Use when authoring TS in `editor/grida-canvas*`, `editor/lib/`, or `packages/*`. Sibling to the `naming` skill; React-specific shape lives in `code-react`.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 19, 2026

Use BEFORE editing any file in `supabase/migrations/` or `supabase/schemas/`, OR when the user runs a `/database` subcommand (`compact local migration`, `rls scenarios`, `align`). Encodes the three contracts that protect the Grida database layer: applied migrations are immutable, RLS implementation mirrors tests (never the reverse), `schemas/*.sql` is the human-readable end-state. Companion to `supabase/AGENTS.md` (RLS, grants, security boundaries).

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 19, 2026

Grida Desktop Electron shell and release-impact work: BrowserWindow, preload, `window.grida`, menus, protocol/deep links, file associations, Forge, path-scoped bridge security, Electron-only UI bugs, and CDP / Playwright verification. Use for `desktop/`, `editor/app/desktop/**`, `editor/scaffolds/desktop/**`, `editor/lib/desktop/**`, `/desktop/*` CSP, GRIDA-SEC-004, and deciding whether linked-package or hosted-renderer changes require a native Desktop version bump or coordinated release. For implementing daemon/agent-tenant core behavior, use `agent-system` as well.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 19, 2026

See all skills by gridaco

Report a problem with this skill