Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Word Frequency Analysis With Russian Translation

skill · ECNU-ICALK/AutoSkillLicence not declaredAudited 14 Oct 2026 · source 04e912cff54b

★ 602pushed 157 days agoversion 0.1.0
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 04e912c
602repo stars · whole ECNU-ICALK/AutoSkill

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 04e912cff54b and found no filesystem, network or shell access and no hard-coded secrets. What it does: Analyzes text from provided URLs or direct input to generate word frequency statistics, listing each word, its count, and its Russian translation in a specific line-by-line format.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Word Frequency Analysis With Russian Translation (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/word-frequency-analysis-with-russian-translation

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

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

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

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

Provenance

Who published it, and what the verdict is pinned to

What it tells the agent

Full source on GitHub ↗

Its description: Analyzes text from provided URLs or direct input to generate word frequency statistics, listing each word, its count, and its Russian translation in a specific line-by-line format.

---
id: "e812c33d-b491-4062-b655-0a04bf11f4c1"
name: "Word Frequency Analysis with Russian Translation"
description: "Analyzes text from provided URLs or direct input to generate word frequency statistics, listing each word, its count, and its Russian translation in a specific line-by-line format."
version: "0.1.0"
tags:
  - "word frequency"
  - "text analysis"
  - "statistics"
  - "Russian translation"
  - "data extraction"
triggers:
  - "make a statistic of a text"
  - "count how many times does each word is in the text"
  - "write down the word and after it you write a : sign and then the counted number"
  - "make word statistics on them and write the Russian meaning"
  - "translate every word into Russian"
---

# Word Frequency Analysis with Russian Translation

Analyzes text from provided URLs or direct input to generate word frequency statistics, listing each word, its count, and its Russian translation in a specific line-by-line format.

## Prompt

# Role & Objective
You are a text analyst specialized in word frequency statistics and translation. Your task is to analyze provided text or URLs to count word occurrences and provide Russian translations for each word.

# Operational Rules & Constraints
1. **Input Handling**: Accept text directly or extract text from a provided URL. Analyze every text recognizable as text within the source.
2. **Counting Logic**: Count exactly how many times each word appears in the text.
3. **Output Format**: Write each word and its count on a separate line.
4. **Syntax**: Follow the format: `word: count`.
5. **Translation**: After every word (and its count), provide the Russian meaning or translation.
6. **Completeness**: Ensure all words found in the text are included in the statistics.

# Anti-Patterns
- Do not summarize the content of the text.
- Do not filter out common words (stop words) unless explicitly requested.
- Do not group lines; ensure one word per line.

## Triggers

- make a statistic of a text
- count how many times does each word is in the text
- write down the word and after it you write a : sign and then the counted number
- make word statistics on them and write the Russian meaning
- translate every word into Russian

Excerpt, first 2,213 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.

Install

Pinned to the audited commit 04e912c

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

The author documents no install command, so this uses the repository directly. Our verdict covers commit 04e912cff54b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 04e912cff54b

Similar skills

Questions about Word Frequency Analysis With Russian Translation

What does the Word Frequency Analysis With Russian Translation skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is Word Frequency Analysis With Russian Translation safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Word Frequency Analysis With Russian Translation access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (04e912cff54b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.