CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 1 flagged

Securityscore 88 · 1 finding

MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · README.md

MEDIUM — it fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.

Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted

excerptREADME.md· markdown

218- English descriptions must start with `Use when ...`

219- Chinese descriptions must use natural Chinese trigger wording, not the English phrase `Use

… (6 chars elided on L219)

220- Do not mention a specific agent in descriptions; describe the user need or task

221- Put longer purpose, capabilities, outputs, and boundaries in `## Overview`

2227. Submit a pull request

Occurrences

1 occurrence · at L220

How to fix

Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.

Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-IMPERATIVE-01sha256682ef7c3e485cf21…rubric 365aacaView on GitHub

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/en/multi-lang-readme/SKILL.md · 1 file

skills/en/multi-lang-readme/SKILL.md3.8 KB · Markdown

name: multi-lang-readme

description: Use when creating bilingual or multilingual README files from an existing README while preserving Markdown structure.

Multi-Lang README

Overview

Create multilingual README files by translating an existing README while preserving Markdown structure, links, code blocks, and language-switch navigation. The workflow supports bilingual and multilingual README sets without rewriting unrelated project documentation.

When to Use

Use this skill when the user asks for:

Bilingual README creation (for example English + Chinese)
Multilingual README generation
Translating an existing README into one or more target languages
Standardized language-switch links across README files

Do not use

Do not use this skill for:

Translating arbitrary non-README documents
Rewriting product requirements or legal documents
Content generation tasks unrelated to README translation

Instructions

Locate the source README file to translate (ask user if ambiguous).
Confirm target language(s) and desired canonical README language.
Translate content while preserving markdown, links, and code blocks.
Write translated files using language suffix conventions.
Add or update language-switch links at the top of each README.
Verify filenames, link paths, and formatting before final output.

Supported Languages

Code	Language
en	English
de	German
ja	Japanese
ko	Korean
zh-CN	Chinese

Workflow

Step 1: Detect README

Find the source README:

Check root directory for README.md
If multiple README files exist, ask which file should be translated

Step 2: Read README Content

Read full markdown content, including:

Title
Badges
All sections (Features, Installation, Usage, Contributing, License, etc.)
Code blocks
Links

Step 3: Confirm Target Language

Ask user which language(s) to translate to. Default assumptions:

README.md should always be in English as the canonical version
If current README is in Chinese (or any non-English), translate it to English first
After English version is established, add other language versions as requested

If user says "create bilingual README" without specifying:

Translate existing README to English first (replace or create README.md)
Then add Chinese version (README.zh-CN.md)

Step 4: Translate with AI

Translate with these rules:

Preserve markdown formatting
Keep code blocks unchanged
Translate section titles to target language
Keep internal links (relative paths) as-is
For external links, use target language anchor text if appropriate

Step 5: Create Translated README

Important: keep README.md as canonical English unless the user explicitly asks for another convention.

English: README.md (create or replace with English version)
German: README.de.md
Japanese: README.ja.md
Korean: README.ko.md
Chinese: README.zh-CN.md

If the original README is non-English and user agrees, replace it with English README.md.

Step 6: Add Language Switcher

Update original README to include language switcher at the top:

**English** | [中文](README.zh-CN.md) | [Deutsch](README.de.md) | [日本語](README.ja.md) | [한국어](README.ko.md)

Add below the title or badges, before the main content.

Step 7: Update Translated README

Add reciprocal link in the translated README:

**[Original](README.md)** | [中文](README.zh-CN.md)

Language Code Reference

en    → no suffix (README.md)
de    → README.de.md
ja    → README.ja.md
ko    → README.ko.md
zh-CN → README.zh-CN.md

Common Triggers

"create bilingual README"
"create English and Chinese README"
"translate README to Japanese"
"add German version of README"
"add README.zh-CN.md"

multi-lang-readme— agent skill

Is multi-lang-readme safe to install?

Multi-Lang README

Overview

When to Use

Do not use

Instructions

Supported Languages

Workflow

Step 1: Detect README

Step 2: Read README Content

Step 3: Confirm Target Language

Step 4: Translate with AI

Step 5: Create Translated README

Step 6: Add Language Switcher

Step 7: Update Translated README

Language Code Reference

Common Triggers

Audit the pieces. Scan the whole. Decide.