autopilot-note

Organize project artifacts into structured notes with routing suggestions.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dmlguq456/agent_setting --skill autopilot-note
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot-note
Source: https://github.com/dmlguq456/agent_setting/tree/main/adapters/claude/skills/autopilot-note
Command: npx skills add https://github.com/dmlguq456/agent_setting --skill autopilot-note

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of scattered project artifacts by transforming generated research, development, experiment, and document outputs into structured notes and routing suggestions that keep knowledge organized.

Core Features & Use Cases

  • Artifact Note Conversion: Reads workflow outputs and creates structured Layer 2 notes with summaries of results, decisions, metrics, and next steps.
  • Knowledge Routing: Matches notes to existing tasks, backbones, papers, and projects while generating triage proposals when connections are unclear.
  • Workflow Maintenance: Supports digest generation, catalog emergence, feedback handling, and idempotent recurring organization workflows for research and engineering environments.

Quick Start

Ask the autopilot-note skill to organize recent project artifacts into notes and provide routing suggestions for review.

Frequently Asked Questions about autopilot-note

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

FAQPage Schema
How do I organize scattered project artifacts into structured knowledge notes?

Knowledge routing for project artifacts matches generated notes to existing tasks, backbones, papers, and projects using metadata routing. When connections are unclear, the system generates triage proposals for manual review to ensure accurate artifact linkage and maintain an organized knowledge base.

How do I automate task tracking and artifact routing for research workflows?

Workflow maintenance for research and engineering environments supports digest generation, catalog emergence, and feedback handling through idempotent recurring organization workflows. This ensures experiment tracking and document workflows maintain an auditable knowledge system over time.

Can I use this for experiment tracking and document workflows?

Yes, you can use this for experiment tracking and document workflows that require artifact summarization and task linkage. It applies deterministic source scanning and review-oriented staging to organize generated outputs into structured notes and routing suggestions across these environments.

What is the best way to summarize project outputs into research notes?

The best way to summarize project outputs into research notes is through artifact note conversion, which reads workflow outputs and creates structured notes with summaries of results, decisions, metrics, and next steps. This process requires deterministic source scanning and metadata routing to maintain an auditable knowledge system.

When do I need review-oriented staging for knowledge management?

You need review-oriented staging for knowledge management when organizing generated project artifacts into structured notes and routing suggestions. This step maintains an auditable knowledge system by ensuring notes are properly matched to existing tasks, backbones, papers, and projects before final catalog integration.