Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Productivity
Paper Engineering Assistant
基于“框架层-总结层-正文层”三层架构的自动化论文写作与文献管理助手。严格按照用户指定的目录（`workspace/毕业论文`）组织所有文件。
skill openclawclawhub Free
基于“框架层-总结层-正文层”三层架构的自动化论文写作与文献管理助手。严格按照用户指定的目录（`workspace/毕业论文`）组织所有文件。
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- _meta.json, SKILL.md, agent.py
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- MRchenkuan
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
1. Skill Description
This skill automates a structured academic writing workflow based on a three-layer architecture: Framework Layer, Summary Layer, and Body Layer. It maintains data consistency across all layers through automatic synchronization mechanisms. The skill operates within a user-designated project directory (default: ./PaperProject/).
2. When to Use
Use this skill when the user needs systematic assistance with academic writing, especially for long-form documents like theses or dissertations. User says: "Start working on my thesis." User says: "Read and structure all literature in the references folder." User says: "Generate a preliminary framework based on my research proposal." User says: "I've modified Section 2.1, please sync the framework and summaries." User says: "Find and download recent literature about 'performance management'."
3. Core Concepts & Workflow
This skill strictly follows the three-layer architecture:
A. Core Three-Layer Structure
Framework Layer (structs.json): The blueprint/map of the entire paper. A JSON array describing the hierarchical structure of chapters, sections, and paragraphs with IDs, titles, abstracts, keywords, and key points. Summary Layer (summaries.json): The content database. Provides detailed summaries for each framework node and records related node IDs for content traceability. Body Layer (./document_body/ directory): The actual written content. A directory and Markdown file collection that exactly mirrors the framework layer structure, with each file corresponding to a writing unit.
B. Workflow Stages
Stage 1: Literature Review & Processing Initialization: Create necessary subdirectories in the project directory (e.g., ./document_body/, ./processed_references/). Process References: Iterate through each reference in the references directory. Create a dedicated folder for each reference (named after the reference) and initialize an information.md file with metadata (title, author, abstract, keywords, download link). If the reference file (e.g., PDF) is available, parse it using the same three-layer architecture, generating corresponding structs.json, summaries.json, and body files stored within that reference's folder. This creates a "knowledge base" for each reference. If the original text cannot be downloaded, only save the information.md. Read Other Materials: Review non-reference materials like research proposals, institutional guidelines, etc., to understand requirements and existing foundations. Stage 2: Document Writing Generate Framework Layer: Create the initial structs.json based on the research topic, proposal, and processed references. If an exemplary reference paper exists, its structure can be emulated. Generate Summary Layer: Write detailed summaries for each framework node, forming summaries.json. Write Body Layer: Based on the framework structure and summary content, write detailed content for each part in the ./document_body/ directory, following the format Chapter_X/Section_X.X_Title.md. If a section becomes too long, split it into multiple files (e.g., Section_X.X_Title_trunc_1.md). Stage 3: Assembly & Synchronization Assemble Final Document: Run a concatenation script that reads all Markdown files in ./document_body/ and merges them in the order defined by the framework layer into a complete thesis_final.md file. This is a programmatic process, not reliant on AI. Critical: Synchronization Mechanism: Top-down Modification: When the user or AI modifies the Framework Layer (structs.json) or Summary Layer (summaries.json), the corresponding Body Layer files must be rewritten or updated. Bottom-up Modification: When the user or AI modifies a Body Layer file, extract its core information to update the corresponding Summary Layer entry and Framework Layer abstract. This synchronization is crucial for maintaining logical consistency and preventing fragmentation, and must be executed after each modification.
4. How to Use (Operating Steps)
When the user triggers the skill, I will work according to the following logic: Confirm Working Directory: I will first establish the project root directory. If not specified, I will use the default ./PaperProject/ in the current working directory. All generated files will be placed within this directory or its subdirectories. Execute the Requested Task: If the request is "start" or "process references": a. Check the directory structure and list all items in the references folder. b. Execute the "Literature Review & Processing" workflow for each item. c. Generate a literature_review_report.md summarizing key findings and interconnections. If the request is "generate framework": a. Comprehensively analyze the research proposal, core insights from processed references, and institutional guidelines. b. Generate or update structs.json (Framework Layer) in the project root. If the request is "write body": a. Read structs.json and summaries.json. b. Create corresponding folders and files in the ./document_body/ directory and begin writing content. Existing files in this directory may be overwritten. c. While writing each section, query summaries.json and the associated reference knowledge bases. If the request is "sync modification": a. The user indicates which file was modified (e.g., ./document_body/Chapter_3/3.1_Current_Analysis.md). b. I first read the modified file content, extract a new abstract and key points. c. Update the section_summary for the corresponding section_id in summaries.json. d. Update the abstract and key_points for the corresponding section_id in structs.json. If the request is "find literature": a. Perform a network search based on the user-provided keywords. b. Attempt to download PDFs to the references directory. c. Create a folder and information.md for each, regardless of download success. If downloaded successfully, proceed with structured parsing. Output & Confirmation: After each operation, I will clearly state which files were generated, their paths, and briefly describe their content.
5. Edge Cases
Directory Doesn't Exist: If the project directory doesn't exist, I will ask the user if they want to create it. References Folder Empty: If the references folder is empty, I will notify the user and ask if they want to proceed directly to framework design or start a network search for literature. Research Proposal Missing: If no research proposal is found, I will generate a very basic initial framework based on the paper title and general academic structure, noting that it will require significant revision. Sync Conflict: If major, irreconcilable discrepancies are detected between the Framework, Summary, and Body layers for the same section, I will list the conflicts and pause automatic synchronization, requesting manual user judgment and instruction.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs1 Scripts1 Config
- SKILL.md
- agent.py
- _meta.json