instructor

Name: instructor
Availability: InStock
Author: neuron-one

Generate step-by-step manuals for manual tasks with TASK, WHY, TIME, STEP-BY-STEP, VERIFY, and ROLLBACK sections.

25|10|Updated Apr 1, 2026

Search Tags:#infrastructure #dns #step-by-step #server-configuration #app-store-submission #manual-task

Ready to run

npx skills add https://github.com/neuron-one/GODMODE --skill instructor-neuron-one

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: instructor
Source: https://github.com/neuron-one/GODMODE/tree/main/skills/infrastructure/instructor
Command: npx skills add https://github.com/neuron-one/GODMODE --skill instructor-neuron-one

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates precise, step-by-step instructions for manual tasks that cannot be automated. Server panel configuration, DNS changes, app store submissions. Use when agent cannot perform the action directly.

Core Features & Use Cases

Produces precise, human-readable, step-by-step manuals for tasks requiring manual intervention.
Includes an explicit OUTPUT format with TASK, WHY, TIME, STEP-BY-STEP, VERIFY, and ROLLBACK sections, plus exact UI element references.
Use cases include configuring servers, updating DNS records, and submitting changes to external services where automation is not possible.

Quick Start

Follow the template to provide exact URLs, button names, and values for the manual task you need completed.

Frequently Asked Questions about instructor

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

FAQPage Schema

How do I create step-by-step instructions for manual server configuration tasks?▼

To create step-by-step instructions for manual server configuration, define the task, purpose, and estimated time, then list exact UI labels, URLs, and verification steps. This structured manual format ensures precise human execution for tasks requiring direct intervention.

What is the best way to document manual DNS changes that cannot be automated?▼

The best way to document manual DNS changes is to use a structured template with TASK, WHY, TIME, STEP-BY-STEP, VERIFY, and ROLLBACK sections. This provides exact URLs and UI labels to ensure the human interaction is repeatable and verifiable.

Can I generate a rollback plan for app store submissions requiring human interaction?▼

Yes, you can generate a rollback plan for app store submissions by defining the manual task in a structured output format. This format explicitly requires a ROLLBACK section alongside step-by-step instructions to safely reverse changes if the external submission fails.

Does this approach work for documenting external service tasks without API automation?▼

Yes, this approach works for documenting external service tasks without API automation by producing human-readable manuals. It captures exact UI element references and step-by-step actions for any manual task where an agent cannot perform the action directly.

What should a manual task template include to ensure precise human execution?▼

A manual task template should include TASK, WHY, TIME, STEP-BY-STEP, VERIFY, and ROLLBACK sections. It must require exact URLs, button names, and input values to ensure the manual instructions are clear, repeatable, and leave no ambiguity for the human executor.

Why do manual infrastructure tasks need a structured output format with verification steps?▼

Manual infrastructure tasks need a structured output format with verification steps to prevent human error during sensitive operations like server configuration. Defining explicit VERIFY and ROLLBACK sections ensures the manual changes are confirmed and safely reversible.