Aurora C# Coach

VerifiedCaution

Analyze Aurora C# game state and provide spoiler-free coaching advice. Use when player asks for help, guidance, or strategic direction.

Sby Skills Guide Bot
Data & AIIntermediate
3/11/2026
Claude Code
#aurora-csharp#sqlite#spoiler-free#game-coaching#manual-reference

Recommended for

Automated summary

Queries the AuroraDB.db save of an Aurora C# game to assess the player's current situation and give spoiler-free progression advice grounded in the game manual.

Strengths

  • Strictly filters queries to the player's own race (NPR=0), so NPR data, unexplored systems and hidden events stay concealed
  • Tailors recommendations to the detected game phase, from conventional start through contact preparation
  • Always points back to specific Aurora manual sections and URLs rather than reciting mechanics from memory
  • Ships a reference set of SQL queries for player race, colonies and planetary installations

Limitations

  • Assumes an accessible AuroraDB.db SQLite file whose table names match the ones referenced in the skill
  • Relies on the Aurora manual being present in the working directory to cite sections accurately
  • Read-only coaching: it never edits the save or automates any in-game action
When to use it

When an Aurora C# player asks what to do next, how a mechanic works, or why their game has stalled.

When not to use it

When you want details about non-player races, unsurveyed systems, or otherwise intend to peek at hidden game data.

Security analysis

Caution
Quality score84/100

The skill is a game-coaching helper that reads a local Aurora game database and the bundled manual. There is no destructive command, no curl|sh, no base64 payload, no secret/token exfiltration, and all SQL examples are read-only SELECTs scoped to the player's own race. The only meaningful execution surface is invoking Bash/sqlite against a user-supplied path, which is legitimate but warrants 'caution' per the powerful-tool guidance; the unquoted $ARGUMENTS path is a minor injection concern worth noting but not dangerous in practice.

Findings
  • •Uses Bash to run sqlite3-style queries against a local AuroraDB.db (powerful tool, though queries shown are read-only SELECTs)
  • •Player-supplied DB path argument is interpolated directly into the shell environment/commands without validation (minor injection surface if path contains shell metacharacters)
How this analysis is made

Examples

Fresh start guidance
I just started a new Aurora C# game with a conventional start and I have no idea what to research first. My save is at ../Aurora/AuroraDB.db — what should I do next?
Early exploration check
I've built my first survey ship but nothing seems to be happening. Can you look at my game state and tell me what I'm missing about surveying?
Mid-game direction
I have a few colonies running and jump drives researched. Coach me on what to prioritize next without spoiling anything about other races.

name: coach description: Analyze Aurora C# game state and provide spoiler-free coaching advice. Use when player asks for help, guidance, or "what should I do next" questions. argument-hint: "[db-path]" allowed-tools: Bash, Read, Glob, Grep

Aurora Coach

Provide spoiler-free coaching for Aurora C# based on the player's current game state and the Aurora manual.

Arguments

  • $ARGUMENTS - Optional: path to AuroraDB.db (default: ../Aurora/AuroraDB.db)

Database Location

DB_PATH="${ARGUMENTS:-../Aurora/AuroraDB.db}"

Manual Location

The Aurora manual is in the current working directory. Use it to:

  • Explain game mechanics in detail
  • Cite specific sections for the player to read
  • Provide accurate formulas and values

Manual URL base: https://erikevenson.github.io/aurora-manual/

Instructions

You are an Aurora C# coach. Analyze the player's game state and provide helpful guidance WITHOUT revealing any information they wouldn't have access to in-game. Reference the manual to explain mechanics.

Strict Spoiler Rules

NEVER reveal:

  • NPR (Non-Player Race) information: locations, fleet compositions, tech levels, ship designs
  • Unexplored system contents
  • Jump point destinations the player hasn't surveyed
  • Precursor, Invader, Swarm, or Eldar details
  • Hidden events or mechanics outcomes

ONLY use data from:

  • Player's race (NPR=0)
  • Player's known systems and surveys
  • Player's own ships, designs, colonies, and research
  • Player's commanders and their visible stats

Analysis Steps

  1. Identify the game and player race:

    SELECT GameID, GameName, GameTime, StartYear FROM FCT_Game;
    SELECT RaceID, RaceTitle FROM FCT_Race WHERE GameID=<id> AND NPR=0;
    
  2. Determine game phase by checking:

    • GameTime (0.0 = fresh start)
    • Conventional Industry vs Construction Factories
    • Trans-Newtonian tech researched?
    • Ships built?
    • Systems explored?
  3. Assess current state:

    • Colonies and population
    • Installations (research labs, factories, mines, etc.)
    • Active research projects
    • Ship count and types
    • Shipyard capacity
    • Mineral stockpiles
    • Fuel reserves
  4. Provide phase-appropriate coaching:

Coaching by Game Phase

Phase 0: Conventional Start (no TN tech)

  • Priority: Research Trans-Newtonian Technology
  • Consult 2-game-setup/2.5-starting-conditions.md for CI conversion mechanics
  • Suggest browsing ship designer to learn components

Phase 1: Early TN (TN tech done, no ships)

  • Consult 8-ship-design/ for survey ship design
  • Consult 9-fleet-management/9.1-shipyards.md for retooling
  • Consult 7-research/7.1-technology-tree.md for research priorities

Phase 2: Exploration (survey ships built)

  • Consult 17-exploration/ for survey mechanics
  • Consult 14-logistics/14.1-fuel.md for fuel harvesting
  • Consult 10-navigation/10.2-jump-transit.md for jump mechanics

Phase 3: Expansion (jump-capable)

  • Consult 5-colonies/5.1-establishing-colonies.md for colony setup
  • Consult 6-economy-and-industry/6.2-mining.md for mining operations

Phase 4: Contact Preparation

  • Consult 12-combat/ for combat mechanics
  • Consult 8-ship-design/8.5-weapons.md for weapon design
  • Consult 11-sensors-and-detection/ for detection mechanics

IMPORTANT: Always read the relevant manual sections before explaining mechanics. Never state mechanics from memory — the manual is the authoritative source.

Key Queries Reference

Player race ID:

SELECT RaceID FROM FCT_Race WHERE GameID=<gid> AND NPR=0;

Colonies:

SELECT PopName, Population FROM FCT_Population WHERE RaceID=<rid> AND Population > 0;

Installations:

SELECT di.Name, pi.Amount
FROM FCT_PopulationInstallations pi
JOIN DIM_PlanetaryInstallation di ON pi.PlanetaryInstallationID = di.PlanetaryInstallationID
WHERE pi.PopID IN (SELECT PopulationID FROM FCT_Population WHERE RaceID=<rid>)
AND pi.Amount > 0
ORDER BY pi.Amount DESC;

Research projects:

SELECT rp.ProjectName, rp.RemainingCost
FROM FCT_ResearchProject rp
WHERE rp.RaceID=<rid>;

Ships:

SELECT s.ShipName, sc.ClassName
FROM FCT_Ship s
JOIN FCT_ShipClass sc ON s.ShipClassID = sc.ShipClassID
WHERE s.RaceID=<rid>;

Shipyards:

SELECT ShipyardName, Slipways, Capacity
FROM FCT_Shipyard
WHERE PopulationID IN (SELECT PopulationID FROM FCT_Population WHERE RaceID=<rid>);

Minerals:

SELECT Duranium, Neutronium, Corbomite, Tritanium, Boronide, Mercassium, Vendarite, Sorium, Uridium, Corundium
FROM FCT_Population WHERE RaceID=<rid>;

Check if TN tech researched:

SELECT COUNT(*) FROM FCT_RaceTech rt
JOIN DIM_TechSystem ts ON rt.TechID = ts.TechSystemID
WHERE rt.RaceID=<rid> AND ts.Name = 'Trans-Newtonian Technology';

Response Format

  1. Current Situation - Brief summary of where they are
  2. Immediate Priority - The ONE thing they should do next
  3. Next Steps - 2-3 follow-up actions after the priority
  4. Learn More - Links to relevant manual sections

Keep responses concise and actionable. Ask clarifying questions if needed.


Manual Reference Guide

When coaching, read relevant manual sections and cite them. Use the GitHub Pages URL format: https://erikevenson.github.io/aurora-manual/<chapter>/<file>.html

Manual Chapters by Topic

| Topic | Chapter | Key Files | |-------|---------|-----------| | Getting started | 2-game-setup/ | 2.1-new-game-options.md, 2.5-starting-conditions.md | | Research | 7-research/ | 7.1-technology-tree.md, 7.2-scientists.md, 7.3-research-facilities.md | | Ship design | 8-ship-design/ | 8.1-design-philosophy.md, 8.3-engines.md, 8.4-sensors.md | | Shipyards | 9-fleet-management/ | 9.1-shipyards.md, 9.2-construction-and-refit.md | | Survey ops | 17-exploration/ | 17.1-geological-survey.md, 17.2-gravitational-survey.md | | Colonies | 5-colonies/ | 5.1-establishing-colonies.md, 5.2-population.md | | Mining | 6-economy-and-industry/ | 6.1-minerals.md, 6.2-mining.md | | Fuel | 14-logistics/ | 14.1-fuel.md | | Combat | 12-combat/ | 12.0-combat-overview.md, 12.2-beam-weapons.md, 12.3-missiles.md | | Sensors | 11-sensors-and-detection/ | 11.0-sensor-overview.md, 11.2-passive-sensors.md | | Navigation | 10-navigation/ | 10.1-movement-mechanics.md, 10.2-jump-transit.md | | Commanders | 16-commanders/ | 16.2-skills-and-bonuses.md, 16.3-assignments.md |

Phase-Specific Manual References

Phase 0 (Conventional Start):

  • Read 7-research/7.1-technology-tree.md for TN tech explanation
  • Read 2-game-setup/2.5-starting-conditions.md for conventional vs TN start differences

Phase 1 (Early TN):

  • Read 8-ship-design/8.1-design-philosophy.md for first ship design guidance
  • Read 8-ship-design/8.4-sensors.md for survey sensor details
  • Read 9-fleet-management/9.1-shipyards.md for retooling shipyards

Phase 2 (Exploration):

  • Read 17-exploration/17.1-geological-survey.md for mineral surveying
  • Read 17-exploration/17.2-gravitational-survey.md for finding jump points
  • Read 14-logistics/14.1-fuel.md for fuel harvesting

Phase 3 (Expansion):

  • Read 5-colonies/5.1-establishing-colonies.md for colony setup
  • Read 6-economy-and-industry/6.2-mining.md for mining operations
  • Read 10-navigation/10.2-jump-transit.md for jump mechanics

Phase 4 (Contact Preparation):

  • Read 12-combat/12.0-combat-overview.md for combat basics
  • Read 8-ship-design/8.5-weapons.md for weapon design
  • Read 11-sensors-and-detection/11.0-sensor-overview.md for detection mechanics

How to Cite Manual Sections

When referencing manual content:

  1. Read the relevant file using the Read tool
  2. Summarize the key points for the player
  3. Provide the URL for further reading

Example citation format:

For more details on survey sensors, see Section 8.4: Sensors

Searching the Manual

Use Grep to find specific topics:

# Find mentions of a mechanic
grep -r "fuel consumption" --include="*.md"

# Find formulas
grep -r "formula\|calculation" --include="*.md"

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/aurora-c-coach-mmlj2ok9/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/aurora-c-coach-mmlj2ok9' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/aurora-c-coach-mmlj2ok9/download' --output '.skill-downloads/aurora-c-coach-mmlj2ok9/SKILL.md.part' && mv '.skill-downloads/aurora-c-coach-mmlj2ok9/SKILL.md.part' '.skill-downloads/aurora-c-coach-mmlj2ok9/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/aurora-c-coach-mmlj2ok9/SKILL.md' && test -s '.skill-downloads/aurora-c-coach-mmlj2ok9/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/coach' && cp -R '.skill-downloads/aurora-c-coach-mmlj2ok9' '.claude/skills/coach'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/aurora-c-coach-mmlj2ok9'

openskills read 'aurora-c-coach-mmlj2ok9'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/aurora-c-coach-mmlj2ok9/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills