8000 Comparing neondatabase:main...bryan-inkeep:main · neondatabase/agent-skills · GitHub
[go: up one dir, main page]
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: neondatabase/agent-skills
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: bryan-inkeep/agent-skills
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 6 commits
  • 4 files changed
  • 3 contributors

Commits on May 22, 2026

  1. add inkeep content writer workflow

    @bryan-inkeep
    bryan-inkeep committed May 22, 2026
    Configuration menu
    Copy the full SHA
    2261045 View commit details
    Browse the repository at this point in the history

  2. Merge pull request #1 from bryan-inkeep/add_gitscript 

    add inkeep content writer workflow
    @bryan-inkeep
    bryan-inkeep authored May 22, 2026
    Configuration menu
    Copy the full SHA
    7bb6853 View commit details
    Browse the repository at this point in the history

  3. feat(neon-auth): add dedicated Neon Auth skill 

    Carves Neon Auth out of the omnibus `neon-postgres` skill into its own
focused skill, mirroring how `neon-postgres-branches` (#19) and
`neon-postgres-egress-optimizer` were split out from the general
Postgres skill.

Neon Auth is a real Neon product surface (provisioning, OAuth providers,
trusted origins, email provider, JWKS) and the `neon-postgres` skill
already mentions it in passing (lines 96-98, 174-181) but does not
walk an agent through provisioning, configuration, or wiring it into an
app. The new skill grounds itself in the Neon MCP server's
`provision_neon_auth`, `get_neon_auth_config`, and `configure_neon_auth`
tools so agents have a deterministic path even when the Neon Console
isn't an option.

Documentation for the Neon Agent Skills overview page on
https://neon.com/docs/ai/agent-skills needs the matching update: a new
"Neon Auth" entry under the list of available skills, and per the
pattern established for other skills, a copy of this SKILL.md should be
discoverable at /docs/ai/skills/neon-auth/SKILL.md.

- `skills/neon-auth/SKILL.md` — new skill (~110 lines, follows the
  existing structure: when-to-use, tool selection, provision, configure,
  wire-up, agent workflow, safety, further reading)
- `README.md` — new "Neon Auth" entry under "Available Skills"

Validated with `npm run validate:skills` (all 5 skills pass).

Co-authored-by: Cursor <cursoragent@cursor.com>
    @bryan-inkeep @cursoragent
    bryan-inkeep and cursoragent committed May 22, 2026
    Configuration menu
    Copy the full SHA
    47767d1 View commit details
    Browse the repository at this point in the history

  4. feat(neon-postgres): add Neon Data API section 

    The `neon-postgres` skill enumerates most Neon product surfaces as
dedicated sections (Neon Auth, Branching, Autoscaling, Read Replicas,
Connection Pooling, Logical Replication, etc.) but the Neon Data API
is only referenced in passing inside the JS SDK paragraph (line 132).

This adds a focused `## Neon Data API` section that:

- Explains when to choose the Data API over a Postgres driver
  (browser/mobile clients, JWT-scoped row-level access).
- Surfaces the MCP provisioning path (`provision_neon_data_api`) so
  agents pick the deterministic tool instead of routing the user
  through the Console.
- Documents the three authentication options (none, Neon Auth, external
  JWKS) without inventing API shapes — each maps directly to a real
  configuration mode in `mcp-server-neon`'s `data_api` scope.
- Links to the canonical Data API get-started page.

Also updates the frontmatter `description` to add Data API triggers
("Neon Data API", "PostgREST", "REST API for Postgres", "HTTP queries
from the browser") so agents activate this skill on those prompts.

Follows the same shape as the existing `## Neon Auth` section and
mirrors the pattern used in PR #24 (the "Branching in CI/CD section"
addition to `neon-postgres-branches`) — extending an existing skill
with a new focused section rather than carving out a whole new skill.

Documentation impact: the public mirror of this skill at
https://neon.com/docs/ai/skills/neon-postgres/SKILL.md (referenced from
this same skill on line 199) needs the matching new section. The Agent
Skills overview page at https://neon.com/docs/ai/agent-skills should
also reflect that the `neon-postgres` skill now covers the Data API.

Validated with `npm run validate:skills`.

Co-authored-by: Cursor <cursoragent@cursor.com>
    @bryan-inkeep @cursoragent
    bryan-inkeep and cursoragent committed May 22, 2026
    Configuration menu
    Copy the full SHA
    e40342e View commit details
    Browse the repository at this point in the history

  5. Merge pull request #3 from bryan-inkeep/feat/neon-postgres-data-api-s… 

    …ection

feat(neon-postgres): add Neon Data API section
    @bryan-inkeep
    bryan-inkeep authored May 22, 2026
    Configuration menu
    Copy the full SHA
    2a9f33a View commit details
    Browse the repository at this point in the history

  6. Merge pull request #2 from bryan-inkeep/feat/neon-auth-skill 

    feat(neon-auth): add dedicated Neon Auth skill
    @bryan-inkeep
    bryan-inkeep authored May 22, 2026
    Configuration menu
    Copy the full SHA
    9741d4f View commit details
    Browse the repository at this point in the history
Loading
0