robel-auth

Enforce upstream-first checks before Convex Auth changes.

9|3|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/get-convex/components-submissions-directory --skill robel-auth-get-convex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: robel-auth
Source: https://github.com/get-convex/components-submissions-directory/tree/main/.codex/skills/robel-auth
Command: npx skills add https://github.com/get-convex/components-submissions-directory --skill robel-auth-get-convex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, npm, and includes scripts (resource) components.

What problem does it solve?

Integrates and maintains Robelest Convex Auth by enforcing upstream-first checks before any auth changes, preventing drift and misalignment with the upstream project.

Core Features & Use Cases

  • Non-negotiable upstream check before any auth change.
  • Reads official docs and compares upstream readmes to guide implementation.
  • Useful for adding auth wiring, migrating upstream patterns, or troubleshooting behavior across projects.

Quick Start

Run the upstream check script before proposing any auth changes to verify current guidance.

Frequently Asked Questions about robel-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent Convex Auth drift when updating upstream integrations?

To prevent Convex Auth drift, enforce upstream-first checks before any auth changes by consulting official docs, comparing upstream READMEs, and verifying branch differences to ensure alignment with the upstream project.

What is the best way to debug Convex Auth behavior across projects?

The best way to debug Convex Auth behavior is to read official documentation and compare upstream READMEs to identify misalignment, ensuring your project's auth wiring matches the current upstream patterns before making changes.

Do I need curl and npm to run the upstream auth verification script?

Yes, you need curl and npm installed because the upstream auth verification script depends on them to fetch official documentation and manage dependency pinning for reproducible auth changes.

When should I pin dependencies during a Convex Auth migration?

You should pin dependencies during a Convex Auth migration when you need to ensure reproducible changes, preventing unexpected upstream updates from breaking your auth wiring after you have verified the current documentation.

Why does my Convex Auth integration break after an upstream update?

Your Convex Auth integration breaks after an upstream update because of drift, which happens when auth changes are made without first verifying upstream documentation and comparing branch differences to catch breaking pattern changes.