Official agent skill

File Server

by microsoft in microsoft/WindowsProtocolTestSuites

ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…

OfficialMITAuto-check passedTesting & QA

Install File Server

skills CLI
$ npx skills add microsoft/WindowsProtocolTestSuites --skill file-server -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/WindowsProtocolTestSuites file-server --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/WindowsProtocolTestSuites.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/file-server .claude/skills/file-server && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
file-server
GitHub stars
567
Token cost
~4.1k tokens
SKILL.md length
1,067 words
Files
12 (incl. references)
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…

  • Works in 3 steps: Identify the Domain by Concepts → Understand the Protocol Document vs Test… → Check Test Location Based on Domain
  • Tasks that involve Test generation
  • SKILL.md covers MANDATORY WORKFLOW (Follow In…, Common Mistakes to Avoid, Protocol-Specific References and Test Scenario Domain…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

File Server is an agent skill from microsoft/WindowsProtocolTestSuites, published by the product's own GitHub organization. ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test implementation. This skill assists with writing FileServer protocol test cases, implementing new test scenarios, discovering reusable libraries, adapters, and transport implementations (TCP, QUIC, NetBIOS, RDMA). CRITICAL--Before implementing any test, first classify the domain by analyzing concepts (File, Fs, FileSystemAttributes…

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/auth.md`, `references/common.md` and `references/dfsc.md`).

It sits in Testing & QA, covering Test generation. The repository describes itself as: ⭐⭐ Join us at SNIA SDC for the SMB3 IO Lab (September 28 - October 1, 2026), see upcoming Interoperability Events. The licence is MIT.

When your agent uses it

  • Tasks that involve Test generation

Example prompts

  • “Use the file-server skill to alway LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA…”
  • “/file-server”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Identify the Domain by Concepts
  2. Understand the Protocol Document vs Test Domain Relationship
  3. Check Test Location Based on Domain

What it can do on your machine

Read from SKILL.md and the folder at commit 29ddb42. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are csharp, xml and powershell).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

File Server loads about 4.1k tokens when it runs, and up to ~48k if it reads all its reference files. Until then it costs about 225 tokens; SKILL.md has 1,067 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~225
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~48k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/WindowsProtocolTestSuites at commit 29ddb42, republished under its MIT licence (© microsoft). 1,067 words, ~4,105 tokens.

Download SKILL.mdSave it as .claude/skills/file-server/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
file-server
description
ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test implementation. This skill assists with writing FileServer protocol test cases, implementing new test scenarios, discovering reusable libraries, adapters, and transport implementations (TCP, QUIC, NetBIOS, RDMA). CRITICAL--Before implementing any test, first classify the domain by analyzing concepts (File*, Fs*, FileSystemAttributes = FSA; NEGOTIATE, SESSION_SETUP, SMB commands = SMB2). Test scenarios from MS-SMB2 that involve File*/Fs* concepts belong to the FSA test suite. Provides test case patterns, storage locations, ProtoSDK usage, and test execution guidance. Protocols under FileServer/src include Auth, Common, DFSC, FSA, FSAModel, FSRVP, RSVD, ServerFailover, SMB2, SMB2Model, and SQOS.
license
MIT
metadata.author
Microsoft
metadata.version
1.2

File Server Test Suite Skill

MANDATORY WORKFLOW (Follow In Order)

You MUST complete these steps IN ORDER. Do not skip ahead.

  1. ☐ CLASSIFY DOMAIN FIRST - Analyze concepts in the scenario (see Test Scenario Domain Classification)
  2. ☐ LOAD THE CORRECT REFERENCE - Based on domain classification
  3. ☐ THEN search for existing tests - Only in the correct domain folder
  4. ☐ Implement or modify - Using the domain-specific patterns

CRITICAL STOP: Do NOT use grep_search or file_search until Step 1 is complete.

MS-SMB2 Document ≠ SMB2 Domain: If the user mentions "MS-SMB2 section X.X.X", DO NOT assume SMB2 domain. First extract the CONCEPTS from the scenario text. If you see File*, Fs*, FileSystemAttributes, FileFsAttributeInformation, or any MS-FSCC structure names → it's FSA domain, regardless of the MS-SMB2 section number.


Common Mistakes to Avoid

MistakeWhy It's WrongCorrect Approach
Searching for tests before classifying domaingrep may find tests in wrong domain (e.g., SMB2 duplicates)Always classify domain FIRST based on concepts
Assuming MS-SMB2 section = SMB2 domainMS-SMB2 often references MS-FSCC structures which are FSA domainCheck the CONCEPTS, not the document source
Finding a test and assuming it's correct locationDuplicate tests may exist in wrong domainsVerify test location matches domain classification

This skill helps you write FileServer protocol test cases by:

  1. Classifying the domain - Determine FSA vs SMB2 vs other based on concepts
  2. Discovering reusable components - Libraries, adapters, and transports you MUST reuse
  3. Providing test patterns - How to structure and where to store test cases
  4. Guiding test execution - Environment configuration and execution methods

Protocol-Specific References

For detailed guidance on specific protocols, load the appropriate reference based on domain classification (see Section 4):

ProtocolReferenceUse When (Domain Indicators)
FSAreferences/fsa.mdConcepts: File*, Fs*, FileSystemAttributes, FileFsAttributeInformation, FileBasicInformation, file system queries, MS-FSCC structures
SMB2/SMB3references/smb2.mdConcepts: NEGOTIATE, SESSION_SETUP, TREE_CONNECT, CREATE, CLOSE, SMB commands, dialects, signing, encryption, compounding
FSA Modelreferences/fsamodel.mdWriting FSA model-based/state-machine tests
DFSCreferences/dfsc.mdDFS, referral, namespace concepts
FSRVPreferences/fsrvp.mdVSS, shadow copy, snapshot, backup concepts
RSVDreferences/rsvd.mdVirtual disk, VHD, VHDX, shared virtual disk concepts
SQOSreferences/sqos.mdStorage QoS, policy, bandwidth, IOPS concepts
Authreferences/auth.mdAuthentication, Kerberos, NTLM, credentials concepts
Failoverreferences/serverfailover.mdFailover, cluster, witness, persistent handle concepts
Commonreferences/common.mdUnderstanding shared infrastructure

Test Scenario Domain Classification (CRITICAL - READ FIRST)

Before implementing any test scenario, you MUST determine its domain based on the CONCEPTS involved, NOT the document section it came from.

CRITICAL STOP: Do NOT use grep_search or file_search until Step 1 is complete. Finding tests via grep does not validate their correct location.

Step 1: Identify the Domain by Concepts

Analyze the test scenario for these keyword patterns:

If scenario mentions...DomainReference to Load
File*, Fs*, FileSystemAttributes, FileFsAttributeInformation, FileBasicInformation, FileStandardInformation, FileInformation*, FsInfo*, FsControl*, file system queries, file attributes, directory informationFSAreferences/fsa.md
NEGOTIATE, SESSION_SETUP, TREE_CONNECT, CREATE, CLOSE, READ, WRITE, IOCTL, LOCK, CANCEL, SMB commands, dialects, signing, encryption, compounding, multichannel, durable handles, leasing, oplocksSMB2references/smb2.md
DFS, referral, namespace, domain-based DFS, standalone DFSDFSCreferences/dfsc.md
VSS, shadow copy, snapshot, backupFSRVPreferences/fsrvp.md
Virtual disk, VHD, VHDX, shared virtual diskRSVDreferences/rsvd.md
Storage QoS, policy, bandwidth, IOPSSQOSreferences/sqos.md
Authentication, Kerberos, NTLM, credentialsAuthreferences/auth.md
Failover, cluster, witness, persistent handlesFailoverreferences/serverfailover.md
Step 2: Understand the Protocol Document vs Test Domain Relationship

IMPORTANT: The MS-SMB2 document describes SMB2 server behavior, but many sections reference MS-FSCC (File System Control Codes) structures. When the test scenario involves:

  • File system information classes (e.g., FileFsAttributeInformation, FileFsVolumeInformation) → FSA domain
  • File information classes (e.g., FileBasicInformation, FileStandardInformation) → FSA domain
  • FSCTL operations (e.g., FSCTL_GET_INTEGRITY_INFORMATION) → FSA domain
  • SMB2 command behavior (e.g., NEGOTIATE, SESSION_SETUP, compound requests) → SMB2 domain

Example: MS-SMB2 section 3.3.5.20.2 describes clearing bits in FileFsAttributeInformation. Even though it's in the SMB2 spec, the concepts (FileSystemAttributes, FileFsAttributeInformation) are FSA domain because they test file system behavior exposed through SMB2.

Show full SKILL.md (445 more words)Show less
Step 3: Check Test Location Based on Domain
DomainTest LocationBase Class
FSATestSuites/FileServer/src/FSA/TestSuite/PtfTestClassBase
SMB2TestSuites/FileServer/src/SMB2/TestSuite/[Feature]/SMB2TestBase
DFSCTestSuites/FileServer/src/DFSC/TestSuite/DFSCTestBase
FSRVPTestSuites/FileServer/src/FSRVP/TestSuite/SMB2TestBase
RSVDTestSuites/FileServer/src/RSVD/TestSuite/RSVDTestBase
SQOSTestSuites/FileServer/src/SQOS/TestSuite/SqosTestBase
AuthTestSuites/FileServer/src/Auth/TestSuite/AuthenticationTestBase / AuthorizationTestBase
FailoverTestSuites/FileServer/src/ServerFailover/TestSuite/ServerFailoverTestBase
Quick Domain Classification Examples
Scenario DescriptionKey ConceptsDomain
"Clear FILE_SUPPORTS_USN_JOURNAL bit in FileFsAttributeInformation"File*, Fs*, attributesFSA
"Server SHOULD clear FileSystemAttributes bits"FileSystemAttributes, File*FSA
"Query FileBasicInformation and verify timestamps"FileBasicInformation, File*FSA
"NEGOTIATE request with signing capability"NEGOTIATE, SMB commandSMB2
"Durable handle reconnect after disconnect"Durable handle, SMB featureSMB2
"Compound CREATE and CLOSE request"Compounding, SMB commandsSMB2
Pre-Implementation Checklist

Before writing or modifying any test, verify:

  • I identified the domain based on concepts (File*, Fs* = FSA; NEGOTIATE, SESSION_SETUP = SMB2)
  • I did NOT assume the domain from the MS-SMB2 document section number
  • I searched for existing tests only in the classified domain folder
  • The test location matches the domain classification table above

1. Reusable Components (MUST REUSE)

ProtoSDK Libraries

Location: ProtoSDK/ - Protocol implementations you MUST reuse.

LibraryPathPurpose
MS-SMB2ProtoSDK/MS-SMB2/SMB2/SMB3 client/server
MS-DFSCProtoSDK/MS-DFSC/DFS referral protocol
MS-FSCCProtoSDK/MS-FSCC/File system control codes
MS-FSRVPProtoSDK/MS-FSRVP/File Server VSS Protocol
MS-RSVDProtoSDK/MS-RSVD/Remote Shared Virtual Disk
MS-SQOSProtoSDK/MS-SQOS/Storage QoS Protocol
TransportStackProtoSDK/TransportStack/TCP, NetBIOS transport
SspiLibProtoSDK/SspiLib/Kerberos, NTLM security
Transport Types

Defined in: ProtoSDK/MS-SMB2/CustomTypes.cs

csharp
public enum Smb2TransportType
{
    Tcp,      // TCP transport (port 445)
    NetBios,  // NetBIOS transport (port 139)
    Rdma,     // RDMA transport (MS-SMBD)
    Quic,     // QUIC transport (port 443)
}
Test Adapters

Location: TestSuites/FileServer/src/Common/Adapter/

AdapterPurpose
Smb2FunctionalClientPrimary SMB2 client - USE THIS for all SMB2 operations
TestConfigBaseConfiguration access (server, credentials, features)
ISutProtocolControlAdapterSUT file/directory operations
Test Base Classes
DomainBase ClassNotes
FSAPtfTestClassBaseAll FSA test classes use public partial class XxxTestCases : PtfTestClassBase
SMB2/SMB3SMB2TestBasepublic class Xxx : SMB2TestBase
DFSCDFSCTestBasepublic class Xxx : DFSCTestBase
FSRVPSMB2TestBaseFSRVP tests inherit from SMB2TestBase (e.g., VSSOperateShadowCopySet : SMB2TestBase)
RSVDRSVDTestBasepublic class Xxx : RSVDTestBase
SQOSSqosTestBaseSqosTestBase : CommonTestBase
AuthAuthenticationTestBase or AuthorizationTestBaseBoth inherit from CommonTestBase
FailoverServerFailoverTestBaseServerFailoverTestBase : SMB2TestBase

2. Test Case Patterns

Where to Store Test Cases
ProtocolDirectory
SMB2TestSuites/FileServer/src/SMB2/TestSuite/[Feature]/
FSATestSuites/FileServer/src/FSA/TestSuite/
DFSCTestSuites/FileServer/src/DFSC/TestSuite/
FSRVPTestSuites/FileServer/src/FSRVP/TestSuite/
RSVDTestSuites/FileServer/src/RSVD/TestSuite/
SQOSTestSuites/FileServer/src/SQOS/TestSuite/
AuthTestSuites/FileServer/src/Auth/TestSuite/
Minimal Test Template
csharp
using System;
using Microsoft.Protocols.TestSuites.FileSharing.Common.Adapter;
using Microsoft.Protocols.TestSuites.FileSharing.Common.TestSuite;
using Microsoft.Protocols.TestSuites.FileSharing.SMB2.Adapter;
using Microsoft.Protocols.TestTools;
using Microsoft.Protocols.TestTools.StackSdk.FileAccessService.Smb2;
using Microsoft.VisualStudio.TestTools.UnitTesting;

namespace Microsoft.Protocols.TestSuites.FileSharing.SMB2.TestSuite
{
    [TestClass]
    public class YourFeatureTests : SMB2TestBase
    {
        private Smb2FunctionalClient client;

        [ClassInitialize()]
        public static void ClassInitialize(TestContext testContext)
        {
            TestClassBase.Initialize(testContext);
        }

        [ClassCleanup()]
        public static void ClassCleanup()
        {
            TestClassBase.Cleanup();
        }

        protected override void TestInitialize()
        {
            base.TestInitialize();
        }

        protected override void TestCleanup()
        {
            if (client != null)
            {
                try { client.Disconnect(); }
                catch (Exception ex)
                {
                    BaseTestSite.Log.Add(LogEntryKind.Debug,
                        "Disconnect exception: {0}", ex.ToString());
                }
            }
            base.TestCleanup();
        }

        [TestMethod]
        [TestCategory(TestCategories.Bvt)]
        [TestCategory(TestCategories.Smb311)]
        [Description("Test description.")]
        public void BVT_Feature_Scenario()
        {
            // Use Smb2FunctionalClient for all SMB2 operations
            client = new Smb2FunctionalClient(TestConfig.Timeout, TestConfig, BaseTestSite);
            client.ConnectToServer(TestConfig.UnderlyingTransport,
                TestConfig.SutComputerName, TestConfig.SutIPAddress);

            // See protocol-specific reference for detailed patterns
        }
    }
}
Test Method Naming

Format: [Category]_[Feature]_[Scenario]

Examples: BVT_Negotiate_SigningEnabled, BVT_Encryption_EncryptedShare

Required Test Categories
csharp
using Microsoft.Protocols.TestSuites.FileSharing.Common.Adapter;

// Test type (pick one)
[TestCategory(TestCategories.Bvt)]    // Build verification
[TestCategory(TestCategories.Model)]  // Model-based

// SMB dialect (for SMB2 tests)
[TestCategory(TestCategories.Smb2002)]
[TestCategory(TestCategories.Smb311)]

// Feature category
[TestCategory(TestCategories.Negotiate)]
[TestCategory(TestCategories.Encryption)]

// Environment (if required)
[TestCategory(TestCategories.DomainRequired)]

3. Test Execution

Configuration Files
FilePurpose
CommonTestSuite.deployment.ptfconfigEnvironment settings (server, credentials)
[Protocol]_ServerTestSuite.ptfconfigProtocol-specific settings
Key Settings in deployment.ptfconfig
xml
<Property name="UnderlyingTransport" value="Tcp"/>  <!-- Tcp, NetBios, Quic -->
<Property name="SutComputerName" value="server.contoso.com"/>
<Property name="SutIPAddress" value="192.168.1.11"/>
<Property name="BasicFileShare" value="SMBBasic"/>
<Property name="MaxSmbVersionSupported" value="Smb311"/>
Running Tests
powershell
# From TestSuites/FileServer/src/Batch/
.\RunTestCasesByFilter.ps1 -Filter "TestCategory=BVT"
.\RunTestCasesByFilter.ps1 -Filter "TestCategory=BVT&TestCategory=Smb311"

# Dry run (list tests without running)
.\RunTestCasesByFilter.ps1 -Filter "TestCategory=BVT" -DryRun
Checking Prerequisites
csharp
using Microsoft.Protocols.TestTools.StackSdk.FileAccessService.Smb2;

// Check dialect
TestConfig.CheckDialect(DialectRevision.Smb311);

// Check feature (skips if unsupported)
BaseTestSite.Assume.IsTrue(TestConfig.IsEncryptionSupported,
    "Test requires encryption support");

4. Decision Tree

Which reference should I load?

First, classify the domain using Step 1 above, then:

  1. FSA domain (File, Fs, file system concepts)?** → Load references/fsa.md
  2. SMB2 domain (SMB commands, protocol features)? → Load references/smb2.md
  3. DFS referral tests? → Load references/dfsc.md
  4. VSS/shadow copy tests? → Load references/fsrvp.md
  5. Virtual disk tests? → Load references/rsvd.md
  6. Storage QoS tests? → Load references/sqos.md
  7. Authentication tests? → Load references/auth.md
  8. Failover tests? → Load references/serverfailover.md
  9. Understanding shared infrastructure? → Load references/common.md

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (references) in .github/skills/file-server of microsoft/WindowsProtocolTestSuites.

  • SKILL.md
  • references/auth.md
  • references/common.md
  • references/dfsc.md
  • references/fsa.md
  • references/fsamodel.md
  • references/fsrvp.md
  • references/rsvd.md
  • references/serverfailover.md
  • references/smb2.md
  • references/smb2model.md
  • references/sqos.md

Open the folder on GitHubat commit 29ddb42

Compare with similar skills

File Server next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

File Server compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
File Server this skillmicrosoft/WindowsProtocolTestSuites567—~4.1kAutomated safety check: PassMIT
Emcaklofas/kicad-happy1.3k1 repos~2.8kAutomated safety check: PassMIT
Swig Testswig/swig6.3k—~2.3kAutomated safety check: PassCustom licence
Generate Test Cases342164796/generate-test-cases1191 repos~2.9kAutomated safety check: PassNone
Verify Cc Safety Netkenryu42/cc-safety-net1.6k—~2kAutomated safety check: PassMIT
Wioworkersio/skills180—~5.8kAutomated safety check: PassMIT

Similar skills

  • Emc

    aklofas/kicad-happy

    EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…

    1.3k GitHub starsUsed in 1 repo~2.8k tokens
    Testing & QAAuto-check passed
  • Swig Test

    swig/swig

    Run SWIG test suite for specific languages. An agent skill from swig/swig.

    6.3k GitHub stars~2.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Generate Test Cases

    342164796/generate-test-cases

    自主学习型测试文档生成器。从需求文档(Markdown)生成测试用例 XMind 文件,支持持久化记忆和持续学习。当用户提到"生成测试用例"、"根据需求生成测试"时触发。

    119 GitHub starsUsed in 1 repo~2.9k tokens
    Testing & QAAuto-check passed
  • Verify Cc Safety Net

    kenryu42/cc-safety-net

    Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence.

    1.6k GitHub stars~2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Wio

    workersio/skills

    Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.

    180 GitHub stars~5.8k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Add E2E Test Suite

    crowdin/crowdin-cli

    Adds a new end-to-end (e2e) test suite for the Crowdin CLI under tests/e2e/suites/, exercising real CLI commands against a freshly-created Crowdin project.

    319 GitHub stars~2.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from microsoft/WindowsProtocolTestSuites

  • Generate Protocol Diff

    microsoft/WindowsProtocolTestSuites

    Official

    Skill for generating diffs between different versions of protocol specifications.

    567 GitHub stars~124 tokensUpdated 22 days ago
    Auto-check passed

Categories

Questions about File Server

What does File Server do?

ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…. File Server is an agent skill from microsoft/WindowsProtocolTestSuites, published by the product's own GitHub organization. ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test implementation.

When should I use File Server?

File Server fits situations like: tasks that involve Test generation.

How do I install File Server in Claude Code?

Run `npx skills add microsoft/WindowsProtocolTestSuites --skill file-server -a claude-code`. Or copy the skill folder (.github/skills/file-server in microsoft/WindowsProtocolTestSuites) into .claude/skills/file-server in your project. Claude Code loads it when a task matches its description.

How do I install File Server in Codex?

Run `npx skills add microsoft/WindowsProtocolTestSuites --skill file-server -a codex`. Or copy the skill folder (.github/skills/file-server in microsoft/WindowsProtocolTestSuites) into .agents/skills/file-server in your project. Codex loads it when a task matches its description.

Can I use File Server in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/WindowsProtocolTestSuites --skill file-server -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/file-server, .gemini/skills/file-server, .github/skills/file-server and .opencode/skills/file-server in your project.

What does File Server need to run?

SKILL.md names no scripts, command-line tools or credentials: File Server is instructions for the agent only.

Does File Server access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is File Server safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does File Server use?

File Server is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does File Server use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 44k tokens, read only when the agent opens those files.

What are the alternatives to File Server?

Skills that share tags, products or a category with File Server: Emc (aklofas/kicad-happy, 1.3k stars), Swig Test (swig/swig, 6.3k stars), Generate Test Cases (342164796/generate-test-cases, 119 stars) and Verify Cc Safety Net (kenryu42/cc-safety-net, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains File Server?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/WindowsProtocolTestSuites, which has 567 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 15, 2026.

Source: microsoft/WindowsProtocolTestSuites on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.