dotnet-sentinel-test

Verify Copilot CLI reads sentinel tokens from sibling reference files.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-sentinel-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-sentinel-test
Source: https://github.com/sayedihashimi/copilot-skill-eval/tree/main/examples/aspnet-razor-pages/plugins/dotnet-artisan/tests/copilot-smoke/fixture-plugin/skills/dotnet-sentinel-test
Command: npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-sentinel-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a lightweight mechanism to verify that Copilot CLI can read and surface content from sibling files referenced within a skill, enabling progressive disclosure during activation smoke tests.

Core Features & Use Cases

  • Verifies that a skill can access and disclose information stored in sibling files to the Copilot CLI during activation.
  • Supports test scenarios for progressive disclosure, ensuring that detailed references remain in separate files while the main skill remains concise.
  • Use Case: Run a smoke test to confirm that the sentinel value in the sibling reference can be retrieved and used to validate access.

Quick Start

Ask Copilot to read the sentinel reference in the sibling file to verify progressive disclosure.

Frequently Asked Questions about dotnet-sentinel-test

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

FAQPage Schema
How do I verify Copilot CLI can read sibling files during skill activation?

You can verify Copilot CLI sibling file access by running a smoke test that checks if the CLI can retrieve a unique sentinel token stored in a companion reference.md file within the skill directory.

What is progressive disclosure in dotnet skills and how does a sentinel test work?

Progressive disclosure keeps detailed references in separate sibling files while the main skill stays concise. A sentinel test validates this by confirming the CLI can read and surface a unique token from a companion reference.md file.

How do I run a smoke test to check sibling file access for .NET-based skills?

To run a smoke test for .NET-based skills, ask Copilot to read the sentinel reference in the sibling file, which validates that the CLI can access and reveal content from companion files in the skill directory.

Do I need a reference.md file to test sentinel values for progressive disclosure?

Yes, testing sentinel values requires a companion reference.md file containing a unique sentinel token. This file ensures the CLI can successfully read and reveal content via sibling references during activation smoke tests.

Why is my Copilot skill not surfacing content from sibling files?

If Copilot is not surfacing sibling file content, your reference.md file may be missing the unique sentinel token or the skill directory structure may prevent the CLI from accessing companion files during activation.

Can I use sentinel smoke tests to validate sibling file access for non-dotnet skills?

Sentinel smoke tests apply specifically to activation tests for .NET-based skills. They validate progressive disclosure and sentinel references across the skill directory, ensuring the CLI can read companion files.