core-engine

Enforce no-fabrication and prose-convention rules across manuscript-writing commands.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/olaTechie/scientific-paper-writer --skill core-engine-olatechie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: core-engine
Source: https://github.com/olaTechie/scientific-paper-writer/tree/main/skills/core
Command: npx skills add https://github.com/olaTechie/scientific-paper-writer --skill core-engine-olatechie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Central engine loaded by every writing command. Enforces no-fabrication guarantees, prose conventions, verification flags, study-type routing, reporting guideline compliance, risk-of-bias tool selection, and expert writing order. All section-specific skills inherit these rules.

Core Features & Use Cases

  • Unified rule governance: no-fabrication guarantee, UK English default, consistency checks.
  • Study-type routing: directs sections to appropriate guidelines based on the selected study design.
  • Cross-section coordination: ensures all manuscript commands conform to expert writing order and risk-of-bias tool selection.

Quick Start

Invoke a writing command to activate the core engine and apply its rules across your manuscript.

Frequently Asked Questions about core-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent data fabrication when writing a research manuscript?▼

Manuscript writing prevents data fabrication by enforcing a no-fabrication guarantee across all commands and inserting verification flags for missing or ambiguous data. It also validates frontmatter fields to ensure strict compliance.

How does study-type routing work for academic manuscript sections?▼

Study-type routing directs manuscript sections to appropriate reporting guidelines based on the selected study design. This ensures correct section ordering, risk-of-bias tool selection, and guideline compliance across the document.

Can I enforce UK English prose conventions across my manuscript?▼

Yes, you can enforce UK English prose conventions by using a centralized writing engine that applies UK English by default and runs consistency checks across all manuscript sections to ensure uniform language usage.

Do I need to install dependencies to use the core engine for manuscript writing?▼

No, you do not need to install dependencies to use the core engine for manuscript writing. It operates without external dependencies and is activated simply by invoking a writing command within your workflow.

What is the best way to coordinate citation handling across different manuscript sections?▼

The best way to coordinate citation handling is through a unified rule governance system that enforces expert writing order and cross-section coordination, ensuring all manuscript commands conform to consistent citation and formatting rules.

Why does my manuscript output include verification flags for ambiguous data?▼

Manuscript output includes verification flags for ambiguous data because the core engine automatically inserts them when data is missing or unclear. This no-fabrication mechanism prevents unverified claims from being published without explicit warnings.