research-log-formatter

Standardize SP-STM Obsidian Research Log notes by validating frontmatter and enforcing body structure.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/xingchen2202/obsidian-ai-knowledge-system --skill research-log-formatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-log-formatter
Source: https://github.com/xingchen2202/obsidian-ai-knowledge-system/tree/main/skills/research-log-formatter
Command: npx skills add https://github.com/xingchen2202/obsidian-ai-knowledge-system --skill research-log-formatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns raw or incomplete SP-STM experiment notes into a standardized, falsification-friendly Research Log by validating required frontmatter, guiding missing fields, and enforcing a consistent note structure.

Core Features & Use Cases

  • Frontmatter completeness validation & repair: Detects missing mandatory fields for Research Log notes and prompts for user confirmation instead of fabricating experimental parameters.
  • Structured note formatting: Inserts recommended sections and ensures the log is readable, consistent, and suitable for downstream analysis and traceability.
  • Safety and provenance guardrails: Enforces anti-hallucination rules (e.g., no invented raw data), preserves existing AI-spec callouts, and performs append-only revision history behavior.
  • Operational creation mode: Generates a new Research Log from a short experiment description while marking unknown values clearly for user follow-up.

Quick Start

Ask Claude to format or create a Research Log when you mention an SP-STM measurement such as “Record today’s STM measurement at 4 K for MnBi2Te4.”

Frequently Asked Questions about research-log-formatter

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

FAQPage Schema
How do I standardize SP-STM experiment notes in Obsidian for auditing?

Formatting SP-STM experiment notes involves validating mandatory frontmatter fields, guiding missing parameters without fabrication, and enforcing a consistent note structure. This process ensures raw experimental records become falsification-friendly and audit-ready.

Can I create a new research log from a brief STM measurement description?

Yes, generating a new research log from a brief measurement description is supported. The tool creates the structured note while clearly marking unknown experimental values for user follow-up instead of fabricating missing parameters.

How does frontmatter validation handle missing experimental parameters?

Frontmatter validation detects missing mandatory fields and prompts for user confirmation. It enforces strict anti-hallucination rules by marking unknown values clearly rather than inventing raw data or experimental parameters.

Does the research log formatting preserve existing Obsidian callouts and revision history?

Yes, the formatting process preserves existing AI-spec callouts and performs append-only revision history behavior. This maintains experimental provenance and ensures downstream analysis traceability for your research logs.

What is the best way to prevent data fabrication when formatting experimental logs?

The best way to prevent data fabrication is enforcing anti-hallucination rules during note formatting. This requires strict MUST-field compliance, unknown-value marking instead of fabrication, and append-only revision history for experimental provenance.

When do I need to insert conclusion cards into my research logs?

Conclusion cards are inserted into research logs when appropriate during the formatting process. They serve as required auditing modules that ensure day-by-day lab documentation remains suitable for review and downstream traceability.