onboard-company

Scaffold company folders, run wiki scrapes, and update memory state atomically.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/aliyehiawi/silt --skill onboard-company
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard-company
Source: https://github.com/aliyehiawi/silt/tree/main/onboard-company
Command: npx skills add https://github.com/aliyehiawi/silt --skill onboard-company

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard a new employer or client into an existing booklet by scaffolding the company folder, running a wiki scrape, and updating memory state in one safe, atomic flow. It ensures you maintain a coherent knowledge graph without overwriting prior data or CLAUDE hot caches.

Core Features & Use Cases

  • Scaffold the company folder structure under memory/work/companies/{slug} with people, projects, and tasks folders.
  • Run an optional wiki scrape to bootstrap company-wide data, glossaries, and past tasks.
  • Atomically flip the previous employer to past on job changes, and update me.md current-state, milestones, roles, and _current pointer. Supports job-change, side-job, client engagements, and re-onboard scenarios.

Quick Start

Invoke onboarding with /onboard-company <slug> to scaffold the folder, optionally run the wiki scrape, and atomically update memory state.

Frequently Asked Questions about onboard-company

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

FAQPage Schema
How do I automate onboarding a new employer into my knowledge vault?

To onboard a new company into your knowledge vault, you invoke the onboarding command with the company slug to scaffold the folder structure, optionally scrape the company wiki, and batch memory state changes for atomic application.

Do I need an initialized memory vault to onboard a new company?

Yes, onboarding a new employer requires an initialized memory vault with an active memory structure, CLAUDE.md linkage, and a wiki connector to safely bootstrap content and write frontmatter-backed files without overwriting prior data.

What happens to my previous employer data when I change jobs in my knowledge graph?

When changing jobs, the onboarding process atomically flips your previous employer to past status, updates me.md current-state and milestones, and shifts the _current pointer, ensuring your knowledge graph remains coherent without overwriting prior employer data.

Can I use this onboarding workflow for contracting clients and side jobs?

Yes, the onboarding workflow supports scaffolding folders for contracting clients, side jobs, and re-onboarding scenarios, applying the same atomic memory state updates and optional wiki scraping tailored to each engagement.

What is the best way to bootstrap company-wide data and glossaries when starting a new role?

The best way to bootstrap company-wide data and glossaries is to run a wiki scrape during the onboarding process, which populates the newly scaffolded company folder with past tasks, glossaries, and relevant documentation.