robel-auth

Validate Convex auth changes against upstream sources before implementation.

3|Updated May 23, 2026

Search Tags:#devops #security #integration #docs #auth #convex #upstream

Ready to run

npx skills add https://github.com/waynesutton/finder9 --skill robel-auth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: robel-auth
Source: https://github.com/waynesutton/finder9/tree/main/.codex/skills/robel-auth
Command: npx skills add https://github.com/waynesutton/finder9 --skill robel-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The skill ensures that auth integration and maintenance for Convex-based apps always consults upstream sources before implementing changes, preventing drift from official patterns.

Core Features & Use Cases

Upstream validation: enforces checking the latest upstream guidance before code changes.
Documentation-driven decisions: requires consulting main and release READMEs plus self-hosting docs when relevant.
Reproducible setup: provides a script and process to verify dependencies and wiring across projects.

Quick Start

Copy this skill into your repo and run bash .agents/skills/robel-auth/scripts/check-upstream.sh to perform the upstream validation before implementing or updating auth.

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 wiring from drifting away from official patterns?▼

To prevent Convex auth wiring drift, you must enforce upstream validation by consulting official documentation and release READMEs before implementing or updating authentication code. This ensures reproducible setups and safe deployments aligned with official sources.

What is the best way to validate Convex auth changes against upstream sources?▼

The best way to validate Convex auth changes is by running an upstream check script, such as check-upstream.sh. This process inspects official docs and performs environment checks to verify dependencies and wiring against the latest upstream guidance.

Can I use upstream validation for debugging existing authentication wiring in Convex apps?▼

Yes, you can use upstream validation when debugging existing authentication wiring in Convex apps. The process requires inspecting official docs and running environment checks to identify and resolve drift from official patterns safely.

When do I need to check upstream documentation for Convex auth integration?▼

You need to check upstream documentation for Convex auth integration whenever you are adding, updating, or debugging authentication wiring. Consulting main and release READMEs plus self-hosting docs prevents pattern drift before code changes are applied.

Does updating Convex authentication require checking self-hosting docs?▼

Yes, updating Convex authentication requires checking self-hosting docs when relevant to your deployment. Documentation-driven decisions are mandatory, meaning you must consult main and release READMEs alongside upstream validation to ensure safe, reproducible setups.