Scientific Writing

Research integrity and tool limits

Only the detailed guide is bundled; research-lookup, venue-templates, schematic/image scripts, LaTeX assets and the other named references are external or absent. Use available authorized source tools and report unavailable literature honestly. Never invent studies, DOI metadata, analyses, ethics approval, consent, registrations, authorship, funding or results. Preserve supplied numbers and uncertainty; verify cited passages support claims and check corrections/retractions. Separate completed methods/results from proposed work, disclose AI help per venue policy, and keep unpublished/private participant data protected. Submission or contact with a journal requires explicit authorization. Reporting checklists aid completeness, not proof of study validity.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use This Skill

This skill should be used when:

• Writing or revising any section of a scientific manuscript (abstract, introduction, methods, results, discussion)
• Structuring a research paper using IMRAD or other standard formats
• Formatting citations and references in specific styles (APA, AMA, Vancouver, Chicago, IEEE)
• Creating, formatting, or improving figures, tables, and data visualizations
• Applying study-specific reporting guidelines (CONSORT for trials, STROBE for observational studies, PRISMA for reviews)
• Drafting abstracts that meet journal requirements (structured or unstructured)
• Preparing manuscripts for submission to specific journals
• Improving writing clarity, conciseness, and precision
• Ensuring proper use of field-specific terminology and nomenclature
• Addressing reviewer comments and revising manuscripts

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.