← Back to Skills Marketplace
mofeiguo

demo-skill

by mofeiguo · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
383
Downloads
0
Stars
5
Active Installs
1
Versions
Install in OpenClaw
/install demo-skill
Description
Generate well-structured technical documents, reports, and summaries with consistent formatting. Use this skill whenever the user asks to write a technical d...
README (SKILL.md)

Demo Document Generator

A skill for generating clean, professional documents with consistent structure.

When to apply this skill

Use this skill for:

  • Technical specifications and feature docs
  • Project reports and status updates
  • API or module documentation
  • Meeting minutes and decision logs
  • README files and onboarding guides

Document Generation Workflow

  1. Understand the document type — identify what kind of document is needed and who will read it
  2. Gather key information — ask only the essential questions (purpose, audience, main content points); don't over-ask
  3. Choose the right template — pick from the templates below based on type
  4. Write the draft — fill in the template with real content, not placeholder text
  5. Review for clarity — ensure each section adds value; cut anything redundant

Templates

Technical Specification

# [Feature/Component Name]

## Overview
One paragraph describing what this is and why it exists.

## Goals
- [Goal 1]
- [Goal 2]

## Non-Goals
- [What this explicitly does NOT cover]

## Design / Approach
Describe the solution, key decisions, and rationale.

## API / Interface (if applicable)
Show the interface, endpoints, or data models.

## Open Questions
- [Unresolved items]

## References
- [Links to related docs or tickets]

Project Status Report

# [Project Name] — Status Update ([Date])

## Summary
One sentence on overall health: 🟢 On track / 🟡 At risk / 🔴 Blocked

## Progress This Period
- [Completed item 1]
- [Completed item 2]

## Next Steps
- [Planned item 1]
- [Planned item 2]

## Risks & Blockers
| Issue | Impact | Owner | Status |
|-------|--------|-------|--------|

## Metrics (if applicable)
| Metric | Target | Actual |
|--------|--------|--------|

Meeting Minutes

# Meeting: [Topic] — [Date]

**Attendees:** [Names]
**Facilitator:** [Name]

## Agenda
1. [Item 1]
2. [Item 2]

## Discussion & Decisions
### [Topic 1]
- Discussion: ...
- Decision: ...

## Action Items
| Action | Owner | Due |
|--------|-------|-----|
| [Task] | [Name] | [Date] |

## Next Meeting
[Date, time, agenda preview]

README / Onboarding Guide

# [Project Name]

> [One-line tagline]

## What is this?
Brief description — what problem does it solve?

## Quick Start
```bash
# Installation and first run

Usage

Core usage examples with real commands or code.

Configuration

Key options and how to set them.

Contributing

How to get started contributing.

License

[License type]


## Writing Principles

- **Lead with the "why"** — readers should immediately understand the purpose
- **Use concrete examples** — show real values, real code, real names; avoid `foo/bar` placeholders
- **Keep sections lean** — one section = one idea; if a section feels thin, fold it into another
- **Tables over lists** for structured comparisons; bullet lists for independent items
- **Active voice** — "The API returns X" not "X is returned by the API"

## Output Format

Always produce the document as a markdown code block so it's easy to copy. If the user seems to want a file saved to disk, write it as a `.md` file in the current directory and tell them where it is.
Usage Guidance
This skill appears coherent and low-risk: it only provides templates and writing instructions and requests no credentials or installs. Two practical things to consider before installing or enabling autonomous use: (1) the skill may create .md files in the current directory when it believes the user wants a saved file — review file paths and contents before trusting or executing any generated commands; (2) always review generated text (especially any suggested shell commands, code samples, or configuration snippets) before running them. If you are uncomfortable with an agent writing files automatically, disable autonomous invocation or instruct the agent to only return content in the chat.
Capability Analysis
Type: OpenClaw Skill Name: demo-skill Version: 1.0.0 The SKILL.md file contains an instruction for the AI agent to 'write it as a .md file in the current directory' if the user wants to save a document. While the explicit intent is to save benign markdown files, this capability grants the agent arbitrary file write access to the current directory. This presents a significant prompt injection vulnerability, as a malicious user could potentially trick the agent into writing files with different extensions (e.g., .sh, .py) or with harmful content, leading to arbitrary code execution or data manipulation. This is a risky capability without clear malicious intent from the skill developer, thus classified as suspicious.
Capability Assessment
Purpose & Capability
The name and description match the SKILL.md templates and workflow. The skill requests no binaries, env vars, or installs, which is appropriate for a text/document-generation utility.
Instruction Scope
SKILL.md stays focused on asking questions, selecting templates, drafting, and reviewing content. One notable instruction: 'If the user seems to want a file saved to disk, write it as a .md file in the current directory and tell them where it is.' Writing files is within the scope of a doc generator but is a runtime side-effect you should be aware of (the agent may create files if it judges the user wants that).
Install Mechanism
No install spec and no code files — instruction-only. This is the lowest-risk model because nothing is downloaded or executed by the skill itself.
Credentials
The skill declares no environment variables, credentials, or config paths. There is no disproportionate request for secrets or external access.
Persistence & Privilege
always:false and no special privileges. The skill does not request persistent system presence or modification of other skills/config; autonomous invocation is allowed by platform default but not escalated here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install demo-skill
  3. After installation, invoke the skill by name or use /demo-skill
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of demo-doc-generator skill. - Enables generation of well-structured technical documents, reports, and summaries with consistent formatting. - Provides ready-to-use templates for specifications, project reports, meeting minutes, and READMEs. - Follows clear document-generation workflow and writing principles to ensure professional quality. - Outputs documents as markdown code blocks for easy copying or file creation
Metadata
Slug demo-skill
Version 1.0.0
License
All-time Installs 6
Active Installs 5
Total Versions 1
Frequently Asked Questions

What is demo-skill?

Generate well-structured technical documents, reports, and summaries with consistent formatting. Use this skill whenever the user asks to write a technical d... It is an AI Agent Skill for Claude Code / OpenClaw, with 383 downloads so far.

How do I install demo-skill?

Run "/install demo-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is demo-skill free?

Yes, demo-skill is completely free (open-source). You can download, install and use it at no cost.

Which platforms does demo-skill support?

demo-skill is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created demo-skill?

It is built and maintained by mofeiguo (@mofeiguo); the current version is v1.0.0.

💬 Comments