Run any Skill in Manus with one click

brain-onboard

Stars0

Forks0

UpdatedJune 20, 2026 at 05:38

Run a structured onboarding interview to collect company, role, strategy, customer, brand, SOP, or source context into staged notes. Use when the user says interview me, onboard me, ask me questions, help populate the brain, collect company context, or turn my answers into notes.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sabirmgd

sabirmgd/company-brain-harness

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	brain-onboard
description	Run a structured onboarding interview to collect company, role, strategy, customer, brand, SOP, or source context into staged notes. Use when the user says interview me, onboard me, ask me questions, help populate the brain, collect company context, or turn my answers into notes.

Brain Onboard

Interview one person and stage structured notes. Do not directly fill final folders.

Workflow

Resolve the brain root.
Read team.yml, company-brain.yml, source-registry.yml, folder indexes, and routing docs if present.
Identify the interview scope: company setup, role setup, customer context, SOP, brand, sales/GTM, engineering/repo, source inventory, or meeting capture.
Ask one question at a time. Keep questions concrete and short.
After 3-6 useful answers, summarize back the candidate note before staging.
Stage notes through stage-brain-note.py --write only when the user wants the proposal saved for review.
Attribute the note to the interviewee and the agent/operator who staged it.
End with what is still missing and which folder should be populated next.

Team Member Prompts

Use these prompts to build a team brain without treating personal accounts as company sources:

What is your role and what decisions do you own?
What workflows do people ask you about repeatedly?
Which company-owned or shared tools do you use?
Which personal tools contain private material and should stay excluded?
Is there a shared Apollo/CRM/meeting/calendar/workspace account the company controls?
What source-derived notes would help the team if curated?
Who should review notes from your area?
What knowledge is stale, wrong, or risky if agents rely on it?
What should route to brain/restricted/ or stay out entirely?

Guardrails

Personal accounts are not company sources.
Sensitive HR/legal/finance material needs restricted routing and explicit owner approval.
If the user does not know an answer, record it as an open question instead of inventing content.
Prefer several small staged notes over one large mixed note.

More from this repository

same repository

brain-contribute

sabirmgd/company-brain-harness

Help a Team Member contribute knowledge safely through a short guided interview or simple drop-zone flow. Use when the user says I want to add what I know, document my role, share my process, add an SOP, update stale facts, suggest team sources, I added a file, or tell the brain about my work.

2026-06-200

brain-intake

sabirmgd/company-brain-harness

Stage or process one document, link, pasted text, transcript, note, or raw artifact into the company brain flow. Use when the user says add this to the brain, ingest this doc, file this note, where should this go, turn this into a brain note, add this document from ADD_TO_BRAIN, or stage this for review.

2026-06-200

brain-operator

sabirmgd/company-brain-harness

Run the daily operator loop for a Company Brain. Use when the user says run today's brain check, do the morning review, check the queue, what needs review, show blockers, check sources, run maintenance, process the ADD_TO_BRAIN folder, I added something to the company brain folder, or give me the next actions.

2026-06-200

brain-owner

sabirmgd/company-brain-harness

Guide the Brain Owner, founder, admin, or team lead through setup and approval decisions. Use when the user says I own this brain, I want to launch the company brain, approve policy, approve sources, choose the operator, choose simple-team or governed mode, invite the team, decide restricted access, or check pilot readiness.

2026-06-200

brain-schedule

sabirmgd/company-brain-harness

Create or update the Company Brain operating schedule for human-gated or autonomous runs. Use when the user says schedule the brain check, set the morning review, automate daily checks, run without a human, keep human in the loop, set cron, or define auto-capture guardrails.

2026-06-200

brain-setup

sabirmgd/company-brain-harness

Scaffold a new team-first Company Brain root without populating company data. Use when the user asks to create the brain files, generate the scaffold, initialize a brain root, create routing, create config, create policy, create source registry, choose the simple automated team model, or run the setup step after owner guidance.

2026-06-200

name	brain-onboard
description	Run a structured onboarding interview to collect company, role, strategy, customer, brand, SOP, or source context into staged notes. Use when the user says interview me, onboard me, ask me questions, help populate the brain, collect company context, or turn my answers into notes.

Brain Onboard

Interview one person and stage structured notes. Do not directly fill final folders.

Workflow

Resolve the brain root.
Read team.yml, company-brain.yml, source-registry.yml, folder indexes, and routing docs if present.
Identify the interview scope: company setup, role setup, customer context, SOP, brand, sales/GTM, engineering/repo, source inventory, or meeting capture.
Ask one question at a time. Keep questions concrete and short.
After 3-6 useful answers, summarize back the candidate note before staging.
Stage notes through stage-brain-note.py --write only when the user wants the proposal saved for review.
Attribute the note to the interviewee and the agent/operator who staged it.
End with what is still missing and which folder should be populated next.

Team Member Prompts

Use these prompts to build a team brain without treating personal accounts as company sources:

What is your role and what decisions do you own?
What workflows do people ask you about repeatedly?
Which company-owned or shared tools do you use?
Which personal tools contain private material and should stay excluded?
Is there a shared Apollo/CRM/meeting/calendar/workspace account the company controls?
What source-derived notes would help the team if curated?
Who should review notes from your area?
What knowledge is stale, wrong, or risky if agents rely on it?
What should route to brain/restricted/ or stay out entirely?

Guardrails

Personal accounts are not company sources.
Sensitive HR/legal/finance material needs restricted routing and explicit owner approval.
If the user does not know an answer, record it as an open question instead of inventing content.
Prefer several small staged notes over one large mixed note.