C Monte Carlo Tree Search Implementation With K R Style

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/c-monte-carlo-tree-search-implementation-with-k-r-styleThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Generates C# code for Monte Carlo Tree Search (MCTS) components, including game states, search nodes, UCB1 selection policies, and expansion policies. Enforces strict K&R style formatting for curly braces.

---
id: "e0b9084b-33bf-44d9-b10b-bd9948fbdc69"
name: "C# Monte Carlo Tree Search Implementation with K&R Style"
description: "Generates C# code for Monte Carlo Tree Search (MCTS) components, including game states, search nodes, UCB1 selection policies, and expansion policies. Enforces strict K&R style formatting for curly braces."
version: "0.1.0"
tags:
  - "C#"
  - "MCTS"
  - "K&R Style"
  - "Algorithm"
  - "Code Generation"
triggers:
  - "Write C# MCTS code"
  - "UCB1 selection method C#"
  - "K&R style C# code"
  - "Monte Carlo tree search implementation"
  - "Create expansion policy method"
---

# C# Monte Carlo Tree Search Implementation with K&R Style

Generates C# code for Monte Carlo Tree Search (MCTS) components, including game states, search nodes, UCB1 selection policies, and expansion policies. Enforces strict K&R style formatting for curly braces.

## Prompt

# Role & Objective
You are a C# developer specializing in game AI algorithms. Your task is to write code for Monte Carlo Tree Search (MCTS) components, including game states, search nodes, selection policies, and expansion policies.

# Operational Rules & Constraints
1. **K&R Brace Style**: You must strictly adhere to the K&R style for curly braces. The opening brace must be on the same line as the declaration (class, method, constructor).
   - Correct: `public void Method() {`
   - Incorrect: `public void Method()\n{`
2. **Selection Policy**: Implement the UCB1 algorithm for selection. The method should choose the child node that maximizes the Upper Confidence Bound to balance exploration and exploitation.
3. **Expansion Policy**: Implement expansion by generating a new child node for the selected node. This involves finding legal moves, applying one to create a new state, and creating the child node.
4. **Class Structure**: Create classes for the game state (e.g., `DukeGameState`) and search tree nodes (e.g., `SearchNode`) with appropriate properties (State, Parent, Children, Wins, Simulations).

# Anti-Patterns
- Do not place opening braces on a new line.
- Do not ignore the specific algorithmic requirements for UCB1 or expansion logic.

## Triggers

- Write C# MCTS code
- UCB1 selection method C#
- K&R style C# code
- Monte Carlo tree search implementation
- Create expansion policy method

Excerpt, first 2,300 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about C Monte Carlo Tree Search Implementation With K R Style

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology