agentleFS
Sign inStart free
Piebald-AIPiebald-AI/splitrail/.claude/skills/types/SKILL.md

types

Skill228 starsChanged 5 months agoMITView on GitHub

Reference for Splitrail's core data types. Use when working with ConversationMessage, Stats, DailyStats, or other type definitions.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. sidorares/node-mysql2★ 4.4ksame name
    2. syntropic137/harness-app-template★ 0same name
    3. syntropic137/software-leverage-points★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read src/types.rs for full definitions.

    line 8
  2. Very specific:

    Use crate::utils::aggregate_by_date() to group messages into daily stats.

    line 29

≈ “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

Key Types

Read src/types.rs for full definitions.

Core Types

  • ConversationMessage - Normalized message format across all analyzers. Contains application source, timestamp, hashes for deduplication, model info, token/cost stats, and role.
  • Stats - Comprehensive usage metrics for a single message including token counts, costs, file operations, todo tracking, and composition stats by file type.
  • DailyStats - Pre-aggregated stats per date with message counts, conversation counts, model breakdown, and embedded Stats.
  • Application - Enum identifying which AI coding tool a message came from.
  • MessageRole - User or Assistant.

Hashing Strategy

  • local_hash: Deduplication within a single analyzer
  • global_hash: Deduplication on upload to Splitrail Cloud

Aggregation

Use crate::utils::aggregate_by_date() to group messages into daily stats. See src/utils.rs.

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.

Check your setup, free