dev-session-contract-probe

Expose a development-only diagnostic endpoint for session integrity and downstream authorization readiness.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill dev-session-contract-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-session-contract-probe
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/dev-session-contract-probe
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill dev-session-contract-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves ambiguity in end-to-end testing by distinguishing between broken authentication cookies and stale downstream runtime dependencies.

Core Features & Use Cases

  • Session Contract Verification: Provides a deterministic way to check if the server-side session contract is intact without exposing sensitive tokens.
  • Downstream Dependency Monitoring: Allows tests to verify if Prism can successfully produce downstream authorization headers.
  • Use Case: During local development or CI testing, use this probe to confirm if a 401 error is caused by an expired session cookie or a failure in the downstream service, preventing flaky test results.

Quick Start

Invoke the dev-session-contract-probe to verify the current authentication session status and downstream readiness.

Frequently Asked Questions about dev-session-contract-probe

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

FAQPage Schema
How do I verify authentication session integrity during local development?

Verify authentication session integrity during local development by invoking a diagnostic probe endpoint that checks server-side session contracts and downstream readiness without exposing sensitive tokens.

What's the best way to debug flaky 401 errors in CI testing?

Debug flaky 401 errors in CI testing by probing the session contract to differentiate between expired session cookies and stale downstream service failures, preventing ambiguous test results.

How does a development diagnostic endpoint check OIDC token presence without exposing credentials?

A development diagnostic endpoint checks OIDC token presence by returning metadata about session validity and authorization readiness, ensuring raw credentials are never exposed during automated testing.

Can I use a session contract probe to monitor downstream authorization header readiness?

Use a session contract probe to monitor downstream authorization header readiness by verifying if your environment can successfully produce downstream authorization headers for automated tests.

Why does my automated testing fail to differentiate between client-side session loss and backend staleness?

Automated testing fails to differentiate between client-side session loss and backend staleness because it lacks a deterministic diagnostic endpoint to probe the server-side session contract and downstream dependencies.

Are there limitations to using a development-only probe for session validity checks?

Development-only probes for session validity checks are limited to local development and CI environments, providing metadata about token presence without exposing credentials or serving production traffic.