blog-resource-access-guard

Enforce blog and resource access controls with author fallback and return paths.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/muddyrain/valley-mas --skill blog-resource-access-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-resource-access-guard
Source: https://github.com/muddyrain/valley-mas/tree/main/.codex/skills/blog-resource-access-guard
Command: npx skills add https://github.com/muddyrain/valley-mas --skill blog-resource-access-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Valley MAS often exposes blog and resource data with inconsistent access controls, leading to mis-visibility, unauthorized access, and broken navigation flows. This skill defines guardrails to enforce correct visibility rules, ensure author self-access handling, and preserve source context across UI states.

Core Features & Use Cases

  • Distinguishes ordinary access permissions from author-management access to ensure private content is visible to authorized users only.
  • Applies to public/details routes, and provides author fallback paths when private data is requested.
  • Preserves source context for cards, detail pages, error pages, and empty states to ensure correct back-navigation and consistent UX.
  • Highlights 404 + return-page scenarios as product bugs requiring remediation rather than mere API issues.

Quick Start

Apply this guard whenever you modify blog or resource access logic to ensure correct visibility, author self-access, and safe back-navigation.

Frequently Asked Questions about blog-resource-access-guard

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

FAQPage Schema
How do I enforce access control for blog and resource routes?

Enforce access control by applying guardrails that distinguish ordinary permissions from author-management access, ensuring private content remains visible only to authorized users while preserving navigation integrity.

How does author self-access fallback work for private blog posts?

Author self-access fallback works by providing author-specific fallback paths when private blog or resource data is requested, allowing content creators to access their own private entries without breaking navigation flows.

Why does my blog detail page return a 404 with a broken back-navigation?

A 404 with broken back-navigation on blog detail pages is a product bug requiring remediation. Guardrails preserve source context for cards, details, errors, and empty states to ensure consistent return paths.

Can I use a navigation guardrail for public, admin, and author views simultaneously?

Yes, navigation guardrails are applicable to public, admin, and author views simultaneously, handling access controls, visibility ranges, and contextual redirects across all route types within the application.

How do I preserve source context across UI states for resource cards?

Preserve source context for resource cards by implementing guardrails that track the origin route, ensuring correct back-navigation and consistent UX across detail pages, error pages, and empty states.

When should I implement optional authentication checks for blog visibility?

Implement optional authentication checks for blog visibility whenever routes expose public, admin, or author views, ensuring that visibility ranges and access controls are enforced before rendering content.