.NET: Why do script and resource not support searching for files in subdirectories?

[JaymzZh]

I have a skill whose script package contains subdirectories. The script isn't searching files in these subdirectories, causing it to fail to execute.

code here:

agent-framework/dotnet/src/Microsoft.Agents.AI/Skills/File/AgentFileSkillsSource.cs

Lines 461 to 472 in f390595

	#if NET
	var enumerationOptions = new EnumerationOptions
	{
	RecurseSubdirectories = false,
	IgnoreInaccessible = true,
	AttributesToSkip = FileAttributes.ReparsePoint,
	};
	foreach (string filePath in Directory.EnumerateFiles(targetDirectory, "*", enumerationOptions))
	#else
	foreach (string filePath in Directory.EnumerateFiles(targetDirectory, "*", SearchOption.TopDirectoryOnly))
	#endif

[SergeyMenshykh]

Which directories are your scripts in? Can you provide your skill structure? The file source looks for skills in the "skills" directory. You can customize the behavior and provide another directory within the skills one if needed: https://learn.microsoft.com/en-us/agent-framework/agents/skills?pivots=programming-language-csharp#customizing-script-discovery

[JaymzZh]

@SergeyMenshykh Thanks for your reply. I have a skill whose scripts directory contains subdirectories, for example:

scripts
  -- xxx1
      -- a.js
  -- xxx2
      -- b.js

The command to execute the script is node scripts/xxx1/a.js. However, our current framework restricts the search to scripts only within the current directory, causing the skill to consistently report a "script not found" error.

The main problem isn't with the customized skill directory, but rather that the search for script files isn't checking subdirectories within that directory.

[SergeyMenshykh]

The scripts/ directory is intentionally scanned non-recursively per the Agent Skills specification, which recommends but does not require keeping file references one level deep.

However, you can configure subdirectories explicitly via AgentFileSkillsSourceOptions.ScriptDirectories. It accepts multi-segment relative paths, so if your scripts are in scripts/lib/ and scripts/utils/, you'd configure:

var options = new AgentFileSkillsSourceOptions
{
    ScriptDirectories = ["scripts", "scripts/lib", "scripts/utils"]
};

Note: this replaces the defaults, so include "scripts" if you still want the root scanned. There's no wildcard/glob support - each subdirectory must be listed explicitly.

[SergeyMenshykh]

We are considering, at the moment, the ways to relax this restriction.

[JaymzZh]

Yes, could we add the RecurseSubdirectories property to the AgentFileSkillsSourceOptions so that the caller can decide whether to traverse subdirectories? Otherwise, the subdirectories for different skills are different, making it impossible to list and set them all in ScriptDirectories.