Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Multi Unit Test Report

v1.0.0

Generate structured markdown test reports for online English classes covering multiple units. Use when the user needs to create a student test report for rev...

0· 46·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for recom273/multi-unit-test-report.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Multi Unit Test Report" (recom273/multi-unit-test-report) from ClawHub.
Skill page: https://clawhub.ai/recom273/multi-unit-test-report
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install multi-unit-test-report

ClawHub CLI

Package manager switcher

npx clawhub@latest install multi-unit-test-report
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The name and description (multi-unit test reports) align with the instructions for extracting slides and producing markdown reports. However, the SKILL.md also requires reading a specific local Obsidian mission-statement file (a hard-coded /Users/... path) that is not necessary for the stated capability and is not declared in the skill metadata.
!
Instruction Scope
Runtime instructions explicitly direct the agent to read local files: the opening slides and summary slides (reasonable if provided by the user) and a specific Obsidian vault file at /Users/recom273/Library/... which is an absolute, user-specific path. The instruction "Always follow the mission statement's guidance" creates an external dependency on that file. The skill does not declare or justify this required file access.
Install Mechanism
No install spec and no code files are present (instruction-only). This minimizes installation risk because nothing is downloaded or written by the skill itself.
!
Credentials
The skill declares no environment variables or config paths, yet the SKILL.md directs access to a local filesystem path (the Obsidian file) and to slide files in folders. The declared requirements do not reflect this filesystem access, which is disproportionate and may expose private local content.
Persistence & Privilege
The skill does not request always:true or any persistent/system-wide privileges. It appears to run only when invoked and to save output to a user-specified folder, which is appropriate for its function.
What to consider before installing
Before installing or enabling this skill, note that SKILL.md instructs the agent to always read a hard-coded Obsidian mission-statement file at /Users/recom273/Library/… — a location on a local machine. That path is user-specific and is not declared in the skill metadata. Risks: the agent may try to read private notes or fail when the file doesn't exist. Recommended actions: (1) Ask the skill author to remove the hard-coded path or make the mission-statement file optional and configurable; (2) require the skill to declare any config paths it needs (or accept mission-statement text supplied at runtime); (3) inspect and/or sanitize the mission-statement file contents before allowing the skill to read it; (4) test the skill in a safe environment (or with a dummy mission statement) to confirm behavior. If you cannot get these clarifications, treat the skill as untrusted because it may access sensitive local files without explicit declaration.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cc86rqay9ae41jxwpybfh6x85hsjq
46downloads
0stars
1versions
Updated 2d ago
v1.0.0
MIT-0

Multi Unit Test Report

Mission Statement

Before generating any report, read the mission statement from the Obsidian vault:

/Users/recom273/Library/Mobile Documents/iCloud~md~obsidian/Documents/Obsidianclaw/projects/system/openclaw/skills/mission statement multi unit test report.md

This file contains the canonical report format, workflow, and improvement suggestions. Always follow the mission statement's guidance for tone and structure.

Workflow

  1. Read the opening slide — Check the top left for the level (e.g., PF3, PF5, PF7) and unit number. This is a review unit covering multiple previous units.
  2. Read all summary slides — These are typically the last slides in the folder. Extract information from each unit reviewed.
  3. Ask about student performance — Ask the user: "Is there anything the student has performed well in?" Incorporate this into the opening praise.
  4. Create an opening sentence praising the student using suggested topics and specific performance notes.
  5. Detail the material covered from each unit, section by section.
  6. Add the standard points to improve — randomly select 3 from the approved list.

Report Structure

Each report follows this exact format (correct typos from the mission statement):

[Opening praise sentence]
# [Student Name]

Todays test covered material from, [unit number]

We featured

**Vocabulary** — [vocabulary topic from all units]

**Grammar** — We learned how to [grammar point from all units][Performance notes]

**Phonics** — We studied the sound [phonic details from all units][Performance notes]

**Around the world** — In this lesson [lesson summary from all units][Performance notes]

**Story** — We read a story about [story synopsis from all units][Performance notes]

**Song** - We ended by singing a song about [song synopsis from all units][Performance notes]

**Life Science** — We learned [science point from relevant units][Performance notes]

**Social Science** — We learned [social science point from relevant units][Performance notes]

**Social Values** — We learned [value point from relevant units][Performance notes]

## Areas for Improvement

It's hard to suggest ways for a student to improve who has just achieved a full score. [select three random points of improvement]

[point 1]
[point 2]
[point 3]

Key Differences from Single Unit Report

  • Multiple units covered — The report summarizes content from 2-3 previous units
  • Review unit format — Opening slide shows "Unit X (Unit Y - Unit Z Review)"
  • Summary slides — Read ALL summary slides at the end (one per unit reviewed)
  • Combined content — Group similar sections across units (e.g., all vocabulary together, all grammar together)

Ways to Improve

Randomly select 3 points from this list:

Points
Its good practice for the future if you read the full sentences including the answer, often in English if the sentence sounds correct then it is correct.
Always read the full sentences aloud. Reading aloud is a good way of identifying any mistakes that you may have made.
Keep practicing! Practice makes perfect.
Speak up! Try to use the freetalk at the beginning of the lesson to expand your conversational ability.
Always review the previous lessons before the final test, this will help you guarantee a 💯 100% score next time.
Try to use full sentences during the lesson, not just one-word answers.
Listen carefully to the questions and make sure you understand before answering.
Don't be afraid to make mistakes - that's how we learn! Keep trying.

Output Location

Save reports to the folder provided by the user. Default to workspace if no location specified.

Comments

Loading comments...