Hire an AI Excel input workbook builder

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• input-form.xlsx, field-rules.md and workbook-handover.md, plus a run register and unresolved-input list.
• A record of source files, changes and check results
• Missing facts and any checks that could not run

How it does the job well

• Turn every request into owned actions: who, what and by when.
• Work from the real calendar, notes and lists. Never invent meetings, people or dates.
• Put the most important decision or deadline first, then the details.
• Prepare drafts and proposals. Sending, booking and changing records waits for approval.

Mistakes it avoids

• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.
• Adding process when a short checklist would do.

What a good result looks like

An example, not your task: Someone else will keep entering data in a workbook you built, and they need a form that rejects bad entries.

• input-form.xlsx. An empty Excel table with dropdowns, entry cells and checks for missing or duplicate records.
• field-rules.md. The rules for every field, plus a separate test copy with made-up records.
• workbook-handover.md. A guide for the next owner with a sheet map, inputs, update steps and checks.
• Run register and open items. What passed, what could not be checked, and which facts are still missing.

How the work is checked

• Every action has an owner and a date, or is marked as missing one.
• Each item points to the note or message it came from.
• The output fits where it will be used, such as one screen or one page.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Build the input form. You confirm the field rules. It builds the empty input table with dropdowns and checks, and tests it on a separate copy with made-up valid, missing and duplicate records.
• Write the handover guide. It documents the form as delivered: the allowed entries, calculated fields, what the checks cannot catch, and how to update it. Then you review the check results.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id prepare-an-excel-input-workbook-for-handover only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/prepare-an-excel-input-workbook-for-handover/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Field definitions, required and allowed values, record key, intended Excel version and the handover owner or process already known.
• The app and file tools your AI can use for the requested work

Tools and access

• An AI that can read Excel files: Lets it inspect the real sheets, formulas and connections, so the guide is checked, not guessed.
• Microsoft Excel: Needed to refresh connections and test the update steps. Without it, steps stay marked as not run.

Functions and deliverables

• Excel input workbook builder: Share field rules, allowed values and Excel version. Get an input workbook, validation checks and a guide for the next owner.
  • input-form.xlsx, field-rules.md and workbook-handover.md, plus a run register and unresolved-input list.
  • A record of source files, changes and check results
  • Missing facts and any checks that could not run
• Excel input form builder: Share field rules. Get an Excel form with dropdowns, clear entry cells and checks.
  • input-form.xlsx and field-rules.md, with an empty production table and a separate illustrative test copy.
  • In the workbook: a form sheet with one column per field and shaded entry cells, a lists sheet holding the dropdown values, and a check column that flags duplicates and missing fields.
  • A record of source files, changes and check results
  • Missing facts and any checks that could not run
• Excel workbook handover writer: Write a handover guide for an Excel workbook so its next owner knows the inputs, formulas, update steps and risks. Your original file stays unchanged.
  • A handover guide, workbook-handover.md, written for the next owner
  • A sheet map and a list of every input with its source, unit and period
  • The key outputs traced back to their formulas, with any hand-typed overrides
  • A numbered update sequence with stop points and what to do if a refresh fails
  • A check table and a list of open items, with what was not run
• Empty workbook builder: Turn a field list you already agreed into an empty Excel workbook or CSV, with clean headings and formats. Use it for a manual register or template.
  • An empty formatted workbook
  • A matching CSV (optional)
  • Clear column headings
  • No invented rows
  Source: sickn33.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• Someone else will keep entering data in a workbook you built, and they need a form that rejects bad entries.
• You want the next owner to have a written guide with the sheet map, the allowed entries and the update steps.
• You want the checks that passed, and the ones that could not run, listed before you hand it over.

Limits to check before starting

• You only need the entry form and nobody else will take it over: use the Excel input form builder.
• You already have a workbook and only need a guide for its next owner: use the Excel workbook handover writer.
• You want to fix broken formulas or compare two versions of a workbook: use the Excel workbook change reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Start a chat with the skill. Open it if you added it to your AI, or copy it and paste it in.
• Supply your actual files and describe the result. The AI checks existing context before asking for missing information.
• Review the native output and its real check evidence before sharing it.
• Send the workbook and guide to the named owner only after every CHECKS row is passed or clearly marked not run.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/prepare-an-excel-input-workbook-for-handover for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.