Skill flagged — suspicious patterns detected

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

Study And Port

v1.2.0

Research new AI frameworks or technologies, extract their best features, evaluate feasibility, and implement as OpenClaw skills. Triggered when: (1) user men...

0· 119·0 current·0 all-time
by邪恶耄耋@chenjin113

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for chenjin113/study-and-port.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Study And Port" (chenjin113/study-and-port) from ClawHub.
Skill page: https://clawhub.ai/chenjin113/study-and-port
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 study-and-port

ClawHub CLI

Package manager switcher

npx clawhub@latest install study-and-port
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description align with behavior: researching frameworks, evaluating portability, and producing SKILL.md + scripts. However, the SKILL.md frontmatter declares 'requires: bins: [node]' and explicit write permissions (~/.openclaw/workspace/skills/ and ~/self-improving/), while the registry metadata above lists no required binaries or config paths — these registry/manifest mismatches should be reconciled.
Instruction Scope
Instructions stay within the stated purpose (search, analyze, rate portability, create skills). They explicitly instruct the agent to create and validate skill files and to read/write persistent progress and procedural-memory files in the user's home. That persistent file I/O is expected for this skill but is material: the agent will create scripts and logs unless the user declines.
Install Mechanism
Instruction-only skill with no install spec or downloaded code. Minimal installation risk because nothing is pulled from external URLs by default. The SKILL.md assumes Node.js is installed (requires bin), but it does not itself install anything.
Credentials
No secrets or external API credentials are requested. The SKILL.md assumes availability of Node.js and a configured MiniMax web search tool (referenced via TOOLS.md) — the registry did not declare these requirements. The write permissions requested are proportional to the stated goal (creating skills and logs) but should be explicitly declared in the registry metadata and approved by the user.
Persistence & Privilege
The skill requests and instructs writing persistent files and scripts under ~/.openclaw/workspace/skills/ and ~/self-improving/. It contains safeguards in prose (always ask before creating, never auto-execute), which mitigate risk if followed, but the ability to create and store executable scripts is a meaningful privilege and should be allowed only after explicit user consent and review of created files.
Assessment
This skill is coherent with its goal of researching frameworks and producing portable SKILL.md or scripts, but it will create files and scripts in your home directories and assumes Node.js and a configured MiniMax search tool. Before installing or enabling it: (1) confirm the registry metadata is updated to declare Node and the write permissions the SKILL.md needs; (2) require the agent to ask for explicit permission before creating any files and to show the exact files it plans to write; (3) review any generated scripts before running them (don't allow auto-execution); (4) ensure the MiniMax tool is properly configured and doesn't expose credentials the skill will use; and (5) if you want to limit risk, restrict or monitor writes to ~/.openclaw/workspace/skills/ and ~/self-improving/. I have medium confidence because the skill is internally consistent with a few manifest mismatches and persistent-write implications that warrant user review.

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

latestvk97311rc3cew1nyan9r7rkpd1585788y
119downloads
0stars
3versions
Updated 1w ago
v1.2.0
MIT-0

Safety & Boundaries

  • Always ask user before creating new skills or scripts
  • Never auto-execute created scripts without confirmation
  • Research only — do NOT implement features that require core OpenClaw changes
  • Report findings to user, let them decide what to keep

Study and Port — Research &移植框架优点

"Don't just use other AI frameworks — learn from them."

When you discover an AI framework or tool with features worth learning, execute this skill.


Trigger Conditions

  • User mentions a new AI framework or tool
  • Discover features in other frameworks that OpenClaw doesn't have
  • Want to learn from other AI assistants' strengths

Workflow

Step 1 — Quick Overview (10 min)

Search endpoint: Use MiniMax web search (configured in TOOLS.md)

Use search to understand:

Template A (General Framework):

"[framework name] features capabilities 2026"
"[framework name] vs OpenAI agent differences"
"[framework name] Hermes Agent comparison"

Template B (AI Coding Assistants):

"[framework name] features capabilities 2026"
"[framework name] self-improving memory workflow"

Template C (Chinese Frameworks):

"[framework name] 特点 功能 优势"
"[framework name] 和 OpenClaw 对比"

Collect:

  • Framework name and version
  • Core features (3-5)
  • Design philosophy
  • How it differs from OpenClaw

Step 2 — Deep Dive (as needed)

For each core feature:

"[framework name]" "[specific feature]" "how it works"
"[framework name]" "implementation" "architecture"

Extract the 3-5 most valuable learnings.

Step 3 — Feasibility Evaluation

For each feature, answer:

Question✅ Yes❌ No
Can this be implemented as SKILL.md?Mark "portable"Mark "requires core change"
Does it need OpenClaw source changes?Mark "requires core"Mark "portable"
Does it need external APIs?Check API availabilityMark "API dependent"
Would users benefit from this?KeepMark "low value"

Portability Rating:

  • 🌟 Portable (skill) — implementable as SKILL.md ± scripts
  • 🔧 Partially Portable — core part doable, limitations exist
  • 🏗️ Requires Core Change — needs OpenClaw source modification
  • Wait & Watch — tech not mature enough

Step 4 — Create Skill (if portable)

User confirmation required: Before creating any new skill or script, ALWAYS ask user:

  • "这个框架的 [功能] 值得移植,我要创建新 skill,可以吗?"

For each "portable" feature:

  1. Write SKILL.md:

    • Clear trigger conditions
    • Detailed execution steps
    • Usage boundaries
    • Script location if needed
  2. Write Scripts (if needed):

    • Scripts must be independently runnable
    • Must handle errors (network failure, file not found, etc.)
    • Node.js runtime must be available (declare in metadata)
  3. Validate:

    ls ~/.openclaw/workspace/skills/[skill-name]/
    node ~/.openclaw/workspace/skills/[skill-name]/scripts/[script].js --help
    

Permissions required:

  • Write access to ~/.openclaw/workspace/skills/ (for new skill files)
  • Write access to ~/self-improving/ (for log files)
  • Node.js runtime (pre-installed with OpenClaw)

Step 5 — Log to Procedural Memory

Append to ~/self-improving/procedural-memory-log.md:

## YYYY-MM-DD

### [Framework] Research
- **Research subject**: [framework name]
- **Features extracted**: [list portable features]
- **Deemed non-portable**: [list with reasons]
- **Skill created**: [skill-name]
- **Portability rating**: 🌟 Fully portable / 🔧 Partially / 🏗️ Core required

Step 6 — Report to User

Tell user:

  • What interesting features were found
  • Which are portable, which aren't
  • What skill was created

Multi-Session Research Tracking

If research spans multiple sessions:

Create ~/self-improving/study-progress.md:

# [Framework] Research Progress

## Started: YYYY-MM-DD
## Status: 🔄 In Progress / ✅ Complete

## Completed
- [ ] Quick overview
- [ ] Core feature analysis

## Pending
- [ ] Feasibility evaluation
- [ ] Skill creation

## Key Findings (update anytime)
-

Read this file when resuming research.


Decision Tree: Should I Port?

Discover new framework
    │
    ▼
Does OpenClaw already have this feature?
    │
    ├─ Yes → Skip, not worth researching
    │
    └─ No or Not Sure → Continue
              │
              ▼
        Would users benefit from this?
              │
              ├─ Not sure → Ask user: "Should I research [framework]?"
              │
              └─ Yes → Continue
                        │
                        ▼
                  Can it be implemented as a skill?
                        │
                        ├─ Yes → Create skill
                        │
                        ├─ Partial → Create core part, note limitations
                        │
                        └─ No (requires core change) → Log to future features

References

  • Procedural Memory System: ../procedural-memory/SKILL.md
  • Skill Creator Guide: ../skill-creator/SKILL.md
  • Self-Improving Memory: ~/self-improving/memory.md

Comments

Loading comments...