CRUX-Utils

Estimate token counts and calculate checksums for CRUX compression workflows.

1|1|Updated Dec 20, 2023
One-click install
npx skills add https://github.com/zotoio/x-fidelity --skill crux-utils
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CRUX-Utils
Source: https://github.com/zotoio/x-fidelity/tree/main/.cursor/skills/CRUX-Utils
Command: npx skills add https://github.com/zotoio/x-fidelity --skill crux-utils

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bc, cksum, awk, basename, tr, and includes scripts (resource) components.

What problem does it solve?

CRUX Utils provides deterministic tooling for token estimation and checksum calculation to support compression workflows.

Core Features & Use Cases

  • Token estimation for CRUX-driven compression planning across code and documents.
  • Checksum generation to align sourceChecksum tracking with CRUX outputs.
  • Use Case: preprocess large repositories to size inputs and verify integrity before applying CRUX rules.

Quick Start

Run the CRUX Utils script with the --token-count option on a target file to obtain a token estimate.

Frequently Asked Questions about CRUX-Utils

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate token counts for files before compression?

You can estimate token counts by running the script with the --token-count option on a target file. This provides deterministic token estimates to size inputs for CRUX-driven compression planning.

Why do I need to calculate checksums in a compression workflow?

Checksum generation aligns sourceChecksum tracking with CRUX outputs to verify input integrity. It ensures files remain unchanged and verifiable before applying compression rules.

What dependencies are required for token estimation and checksum calculation?

Token estimation and checksum calculation require bc, cksum, awk, basename, and tr. These standard command-line utilities ensure deterministic analytics for preprocessing pipelines.

Can I use bash scripts to preprocess large repositories for compression?

Yes, you can use this bash scripting tool to preprocess large repositories. It sizes inputs and verifies integrity across code and documents before applying CRUX compression rules.

What is the best way to verify file integrity before applying CRUX rules?

The best way to verify file integrity is by generating checksums using cksum. This aligns sourceChecksum tracking with CRUX outputs to detect any data corruption before processing.

Are there limitations when using bash for deterministic token estimates?

Deterministic token estimates rely on bc and awk for calculation, meaning limitations stem from the shell environment. The script depends on these specific utilities being installed and accessible.