Add gipity plugin (GipityAI/skills)

[siverson914]

What this PR does

New plugin: adds the Gipity plugin to the catalog as a remote source.

• Plugin name: gipity
• Type: remote source
• Source URL + pinned SHA: https://github.com/GipityAI/skills.git @ 90fd54797da9dc4e2ab435dc801eba743f6a538c
• Homepage: https://gipity.ai

Gipity is a full-stack cloud platform for coding agents - hosting, Postgres databases, serverless functions, auth, file storage, realtime, and AI services, all driven by the gipity CLI. The plugin's skills cover onboarding plus the most common builds (full-stack web apps, 2D/3D games, computer vision, realtime), and its hooks keep a linked project's files auto-synced to the cloud. Verified against Grok Build 0.2.99: grok plugin install GipityAI/skills --trust discovers all 10 skills, the /gipity:setup command, and the hooks (grok plugin validate passes).

Ownership

• I own this plugin or have the right to distribute it.
• The source repo is published under our official org (GipityAI).

Checklist

• Added/updated exactly one entry in .grok-plugin/marketplace.json (valid JSON, kebab-case name).
• Remote source pins a full 40-char lowercase commit sha, and that commit is public + reachable.
• Regenerated .grok-plugin/plugin-index.json (python3 scripts/generate-plugin-index.py).
• python3 scripts/validate-catalog.py passes locally.
• python3 scripts/generate-plugin-index.py --check passes locally.
• homepage + clear description set; local plugins include README.md + .grok-plugin/plugin.json.
• License is stated (MIT, in the source repo's plugin.json and LICENSE).

Security

• No curl | bash, remote-code download/exec, or postinstall RCE.
• No reading/exfiltration of secrets, tokens, .env, or env vars.
• Hooks and MCP scope are least-privilege.
• Network endpoints this plugin calls (and why): the hooks run the user-installed gipity CLI, which calls *.gipity.ai (Gipity's own API - file sync, deploys). Every hook checks for a .gipity.json project marker in the working directory first and exits immediately outside Gipity projects; nothing runs or phones home in other repos.
• Credentials/permissions it requires (and why): the user's own Gipity account session, created interactively via gipity login (email + 6-digit code). The plugin stores no secrets and requires no API keys.

Notes for reviewers

The skills are generated from the same documentation source that powers Gipity's hosted agent and docs site (single source of truth), and the repo doubles as the plugin's Claude Code marketplace - it's the canonical distribution point. Session-capture hooks explicitly no-op under Grok (guarded on GROK_HOOK_EVENT); only file-sync hooks are active. The gipity CLI on the machine is installed by the user (npm install -g gipity), not by this plugin.