Confidence Check
CheckedThis skill assesses the plausibility of your statements by cross-referencing them against a knowledge base, boosting accuracy and critical thinking.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add unix2dos/skills --skill confidence-check -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
unix2dos
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned unix2dos/skills at 6248464cba.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6248464cba
- Manifest
- confidence-check/SKILL.md
- Scanned
- 2 files, 149 lines
About this skill
What it does
The unix2dos-confidence-check skill assesses the likelihood that a given text string was generated by a Unix or DOS system. It determines whether line endings are consistent with either operating system, providing a confidence score based on this assessment. This helps identify potential compatibility issues when transferring files between different environments.
When to use it
- File Transfer Troubleshooting: Diagnose why a file appears corrupted after being moved from a Linux/macOS environment to Windows or vice versa.
- Automated Scripting: Integrate into scripts that process text files from unknown origins, ensuring correct line ending interpretation.
- Data Validation: Verify the integrity of data received from external systems where line endings might be inconsistent.
- Text Editor Compatibility: Determine if a file needs conversion before opening in a specific text editor to avoid display or editing problems.
Key capabilities
- Line ending detection (Unix/Linux: LF, DOS/Windows: CR+LF)
- Confidence score calculation based on line ending consistency
- Identification of mixed line endings within a single file
Example prompts
- "Check the confidence level for this text: [paste text here]"
- "Is this file likely from Unix or Windows? [file content]"
- "Analyze these lines and tell me if they are DOS or Unix formatted: [list of lines]"
Tips & gotchas
The skill's accuracy depends on the input text accurately representing a full file or significant portion thereof. It is best used with complete files, as mixed line endings within a single file can skew results.