agentleFS
SecuringTheRealmSecuringTheRealm/str-agentic-adventures/.claude/skills/agent-framework/SKILL.md

agent-framework

Skill4 starsChanged 6 months agoMITView on GitHub

Triggers when the agent creates or modifies AI agents, registers tools, or changes fallback logic. Covers Microsoft Agent Framework SDK patterns, singleton client, and thread management.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use singleton azure_openai_client from backend/app/azure_openai_client.py

    line 9
  2. Very specific:

    Never instantiate AzureOpenAIClient() directly

    line 10
  3. Very specific:

    All agents use AgentClientManager from backend/app/agent_client_setup.py

    line 14
  4. Very specific:

    All agents MUST check azure_openai_client.is_configured()

    line 24
  5. Distinctive:

    When False: use deterministic game logic, never call Azure

    line 25
  6. Very specific:

    Create threads with agent_client_manager.create_thread()

    line 29
  7. Distinctive:

    Use threads to maintain conversation context across interactions

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Microsoft Agent Framework Patterns

Client Access

  • Use singleton azure_openai_client from backend/app/azure_openai_client.py
  • Never instantiate AzureOpenAIClient() directly
  • Uses DefaultAzureCredential (managed identity in Azure, az login locally)

Creating Agents

  • All agents use AgentClientManager from backend/app/agent_client_setup.py
  • Create with agent_client_manager.create_agent(name, instructions, model, tools, temperature)
  • Store agent references for reuse via module-level singletons

Tool Registration

  • Use agent_client_manager.create_function_tool(name, description, parameters, callable_fn)
  • Include clear descriptions and typed parameters
  • Tools are registered at agent creation time

Fallback Mode

  • All agents MUST check azure_openai_client.is_configured()
  • When False: use deterministic game logic, never call Azure
  • Wrap Azure SDK calls in try-except with context logging

Thread Management

  • Create threads with agent_client_manager.create_thread()
  • Use threads to maintain conversation context across interactions
  • One thread per game session per agent

Architecture Decision

  • See ADR-0018 for migration rationale
  • SDK: azure-ai-projects>=1.0.0,<2.0.0
  • API version: 2025-05-01

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.