Skill flagged — suspicious patterns detected

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

officecli-academic-paper

v1.0.1

Use this skill when the user wants to create an academic paper, research paper, white paper, technical report, policy brief, or any formally structured docum...

0· 113·1 current·1 all-time
by瓦砾@iceyliu

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for iceyliu/officecli-academic-paper.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "officecli-academic-paper" (iceyliu/officecli-academic-paper) from ClawHub.
Skill page: https://clawhub.ai/iceyliu/officecli-academic-paper
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 officecli-academic-paper

ClawHub CLI

Package manager switcher

npx clawhub@latest install officecli-academic-paper
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
The skill's name, description, and detailed instructions all align with building formally structured .docx documents and therefore legitimately require an officecli-like binary. However, the SKILL.md assumes availability of a third-party binary and embeds an imperative install/upgrade procedure (curl + bash) that is not declared in the registry install metadata — a mild inconsistency between claimed packaging and runtime requirements.
!
Instruction Scope
The runtime instructions explicitly instruct the agent to fetch and execute remote scripts and to call network endpoints (curl to raw.githubusercontent.com and to the GitHub API). They require the agent to run arbitrary shell commands (install/update scripts) and to perform auto-upgrades before each use. While the document-manipulation commands themselves stay on-purpose, the unconditional download-and-execute step grants the agent broad ability to run arbitrary code fetched at runtime and to modify the host environment.
!
Install Mechanism
There is no declared install spec, but SKILL.md tells the agent to run curl -fsSL https://raw.githubusercontent.com/iOfficeAI/OfficeCli/main/install.sh -o /tmp/officecli_install.sh && bash /tmp/officecli_install.sh. Downloading and executing an arbitrary install script at raw.githubusercontent.com (even from a GitHub repo) is high risk because the script can run any commands. The SKILL.md also instructs automated upgrades using the same mechanism.
Credentials
The skill does not request any environment variables, credentials, or config paths. The lack of secret/credential requests is appropriate for a document-creation tool and reduces direct exfiltration risk. However, the install/update commands could still cause indirect risk by executing code with the agent's privileges.
!
Persistence & Privilege
The skill does not set always:true, but the instructions will install or upgrade a system binary at runtime and potentially make persistent changes on the host (files under /usr/local, /tmp execution, etc.). If the agent is allowed to invoke the skill autonomously, it could cause repeated network fetch-and-execute cycles. This persistent modification behavior is not surfaced in the registry metadata.
What to consider before installing
This skill appears to be what it says (a recipe for producing academic .docx files), but the SKILL.md tells the agent to download and execute an install script from raw.githubusercontent.com and to auto-upgrade from GitHub before each use. That is the main risk. Before installing or running this skill: - Do not run the curl | bash command blindly. Inspect the install.sh contents at https://raw.githubusercontent.com/iOfficeAI/OfficeCli/main/install.sh to confirm it is safe and from a trusted maintainer. - Prefer installing officecli manually from a vetted package or repository (or pin a specific, signed release) rather than allowing automatic unpinned installs/upgrades. - If possible, run the skill in an isolated environment (container or VM) so the remote install cannot affect your primary system. - If you do not want the agent to fetch or execute remote code automatically, remove or comment out the install/upgrade block in SKILL.md or configure the agent to require explicit confirmation before running shell commands that fetch remote scripts. - Consider asking the skill author to provide an explicit install spec (packaged release URL or package-manager entry) and to avoid curl|bash auto-updates in runtime instructions. Given these factors, treat this skill as suspicious until you verify the install script and are comfortable with its runtime network/execution behavior.

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

latestvk9704nj3t0jf3bbv282vsd4f39840m4f
113downloads
0stars
2versions
Updated 3w ago
v1.0.1
MIT-0

Academic Paper Skill

Create formally structured Word documents with Table of Contents, equations (LaTeX to OMML), footnotes/endnotes, bibliography, and scholarly formatting. Output is a single .docx file. This skill supersedes the docx creating.md Academic Paper recipe -- use THIS skill for any document requiring TOC + equations + footnotes + formal structure.


BEFORE YOU START (CRITICAL)

Every time before using officecli, run this check:

if ! command -v officecli &> /dev/null; then
    echo "Installing officecli..."
    curl -fsSL https://raw.githubusercontent.com/iOfficeAI/OfficeCli/main/install.sh -o /tmp/officecli_install.sh && bash /tmp/officecli_install.sh && rm -f /tmp/officecli_install.sh
    # Windows: irm https://raw.githubusercontent.com/iOfficeAI/OfficeCli/main/install.ps1 -OutFile "$env:TEMP\officecli_install.ps1"; & "$env:TEMP\officecli_install.ps1"
else
    CURRENT=$(officecli --version 2>&1 | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
    LATEST=$(curl -fsSL https://api.github.com/repos/iOfficeAI/OfficeCLI/releases/latest | grep '"tag_name"' | sed -E 's/.*"v?([0-9.]+)".*/\1/')
    if [ "$CURRENT" != "$LATEST" ]; then
        echo "Upgrading officecli $CURRENT -> $LATEST..."
        curl -fsSL https://raw.githubusercontent.com/iOfficeAI/OfficeCli/main/install.sh -o /tmp/officecli_install.sh && bash /tmp/officecli_install.sh && rm -f /tmp/officecli_install.sh
    else
        echo "officecli $CURRENT is up to date"
    fi
fi
officecli --version

Use When

  • User wants to create a research paper, journal manuscript, or conference paper with academic structure (abstract, numbered sections, references)
  • User wants a white paper, policy brief, or technical report with formal structure (executive summary, TOC, branded headers)
  • User needs math equations (LaTeX to OMML) in a Word document
  • User needs footnotes, endnotes, or bibliography with hanging indent
  • User needs a Table of Contents that auto-updates in Word
  • User mentions "APA", "MLA", "Chicago", or any citation style formatting
  • User needs multi-column abstract or mixed portrait/landscape sections

Don't Use When

  • User wants a general letter, memo, contract, or simple report -- use docx skill
  • User wants a presentation -- use pptx skill
  • User wants a spreadsheet or dashboard -- use xlsx or data-dashboard skill
  • User needs LaTeX output (.tex file) -- this skill produces .docx only
  • User needs graduate thesis with Roman numeral front-matter pagination -- deferred to Phase 2
  • User needs tracked changes or collaborative editing markup -- use docx skill with raw-set

What This Skill Produces

A single .docx file with:

ComponentDescription
Cover / title blockCentered title, authors, affiliations
Table of ContentsNative Word TOC field (levels 1-3), updateable
Structured sectionsHeading1/2/3 hierarchy with consistent styling
EquationsDisplay and inline OMML from LaTeX subset
Footnotes / endnotesInline references at correct paragraph positions
BibliographyHanging indent, per-citation-style formatting
Headers / footersPage numbers, optional branding
Optional: watermark, charts, custom bordered blocks, cross-references

Core Concepts

Style-First Architecture (NON-NEGOTIABLE)

Define ALL styles before adding ANY content. Skipping style definitions causes formatting failures in 100% of cases. Different Word versions define Heading1 as 14pt, 16pt, or 13pt -- explicit style setup eliminates this variance.

Font Size Hierarchy

StyleSizeWeightspaceBeforespaceAfter
Heading1>= 16ptbold360 (18pt)120 (6pt)
Heading2>= 14ptbold360 (18pt)80 (4pt)
Heading3>= 12ptbold + italic240 (12pt)80 (4pt)
Body (Normal)11-12ptregularper paper typeper paper type
Caption9-10ptitalic----
FootnoteText9-10ptregular----

Verified LaTeX Subset

CategoryLaTeXNotes
Fractions\frac{a}{b}Nested supported
Sub/superscriptsx_i, x^{n+1}Multi-char needs braces
Summation\sum_{n=1}^{\infty}Limits above/below in display
Integration\int_0^{\infty}, \ointSingle, double, and contour
Products\prod_{i=1}^{n}
Limits\lim_{x \to 0}
Square roots\sqrt{x}, \sqrt[3]{x}nth-root supported
Greek letters\alpha .. \OmegaBoth cases
Nabla / partial\nabla, \partial
Accents\hat{x}, \bar{x}, \tilde{x}, \vec{x}, \dot{x}
Bold math\mathbf{x}For vectors
Aligned\begin{aligned}...\end{aligned}Multi-line systems
Matrices\begin{pmatrix}...\end{pmatrix}Also bmatrix, vmatrix
Angle brackets\langle, \rangleFor bra-ket notation
Simple delimiters\left[...\right]ONLY when NO sub/super inside
DO NOT USE\left[...\right] + subscript/superscript insideCast error crash
DO NOT USE\left(...\right) + subscript/superscript insideSame crash
DO NOT USE\mathcal{L}Invalid XML -- use \mathit{L}

Footnote Behavior

Footnotes are inline reference runs within the target paragraph. They do NOT create new paragraphs and do NOT shift paragraph indices. You can add footnotes in any order -- forward, reverse, or arbitrary. The old "reverse order" advice is obsolete as of v1.0.24.


Workflow Overview

Phase 1: Analyze Input

Classify paper type (social science, physics/math, white paper). Look up the Feature Selection Table in creating.md Section A. Plan which sections to follow.

Phase 2: Setup

Create document, set defaults + margins, define ALL styles upfront. Plan section breaks if multi-column or landscape is needed.

Phase 3: Build

Add content in order: cover, TOC, abstract, body sections, equations, tables, footnotes, bibliography, headers/footers, watermark.

Phase 4: QA

Run verification loop: validate, view outline, view issues, view text. Fix and re-verify.


Quick Reference: Key Warnings

WarningDetail
\left/\right + sub/superCrashes with cast error. Use plain (), [] -- OMML auto-sizes.
pbdr at style leveladd /styles --prop pbdr.all=... is silently dropped. set /styles/X --prop pbdr.all=... is rejected. Always set borders per-paragraph after creation.
Section break +1 offsetEach section break inserts one empty paragraph into /body. Account for +1 index offset on all subsequent p[N] references.
Shell escaping for LaTeXDouble backslashes in bash: --prop "formula=\\frac{a}{b}". Use heredoc for complex formulas.
Dollar sign $ in textBash expands $ as variable in double quotes. Use single quotes or \$. See creating.md D-10.
Batch JSON valuesALL values must be strings: "true" not true, "24" not 24.
Batch intermittent failure~1-in-15 failure rate. Retry on error. Keep arrays to 10-15 max.

Quick Start (Social Science Paper Skeleton)

officecli create paper.docx
officecli set paper.docx / --prop defaultFont="Times New Roman"
officecli set paper.docx '/section[1]' --prop marginTop=1440 --prop marginBottom=1440 --prop marginLeft=1440 --prop marginRight=1440
officecli add paper.docx /styles --type style --prop id=Heading1 --prop name="Heading 1" --prop type=paragraph --prop font="Times New Roman" --prop size=16 --prop bold=true --prop spaceBefore=360 --prop spaceAfter=120 --prop keepNext=true
officecli add paper.docx /body --type toc --prop levels=1-3 --prop title="Table of Contents"
officecli add paper.docx /body --type paragraph --prop text="Introduction" --prop style=Heading1
officecli add paper.docx /body --type paragraph --prop text="This paper examines..." --prop size=12 --prop lineSpacing=2x

Follow creating.md for the full step-by-step guide.


References

Comments

Loading comments...