hydra-gate-admin-router

Detect insecure Vue component registrations in Nextcloud router files.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-admin-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hydra-gate-admin-router
Source: https://github.com/ConductionNL/shillinq/tree/main/.claude/skills/hydra-gate-admin-router
Command: npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-admin-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents security vulnerabilities caused by incorrectly registering admin-only Vue components as public frontend routes, which would otherwise bypass Nextcloud's server-side access controls.

Core Features & Use Cases

  • Route Auditing: Scans router configuration files to detect unauthorized exposure of admin settings components.
  • Compliance Enforcement: Ensures adherence to ADR-004 by validating that admin settings are handled exclusively through the Nextcloud settings framework.
  • Use Case: During a code review or CI/CD pipeline, use this Skill to automatically verify that no developer has accidentally exposed an admin dashboard component via the frontend router.

Quick Start

Run the hydra-gate-admin-router skill to audit the current repository router configuration for unauthorized admin route definitions.

Frequently Asked Questions about hydra-gate-admin-router

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

FAQPage Schema
How do I detect insecure Vue component registrations in Nextcloud router files?

To detect insecure Vue component registrations in Nextcloud router files, you need static analysis to scan router configurations and flag admin-only components exposed as public frontend routes. This prevents bypassing server-side access controls.

Why does exposing admin settings components via the frontend router bypass Nextcloud access controls?

Exposing admin settings components via the frontend router bypasses Nextcloud access controls because public routes lack server-side authorization checks. This allows unauthorized users to access administrative dashboards directly through the frontend application.

How do I enforce ADR-004 compliance for Nextcloud admin route isolation?

To enforce ADR-004 compliance for Nextcloud admin route isolation, audit router configuration files to validate that admin settings are handled exclusively through the Nextcloud settings framework rather than public frontend routes.

Can I use a router security audit as a CI/CD pipeline gate for Nextcloud applications?

Yes, you can use a router security audit as a CI/CD pipeline gate for Nextcloud applications. The static analysis automatically verifies router configurations during code review to prevent developers from accidentally exposing admin dashboard components.

What is the best way to prevent unauthorized exposure of Nextcloud admin components?

The best way to prevent unauthorized exposure of Nextcloud admin components is implementing automated static analysis on router configuration files. This ensures architectural security standards are met by verifying admin settings route exclusively through the Nextcloud settings framework.