Setup Workspace

Community

timscheuerai

setup-workspace

Initialize this content workspace for a new author, including local preferences and optional Notion or local search setup.

Overview

Publisher	timscheuerai
Repository	`linkedin-funnel`
Skill name	`setup-workspace`
Stars	60
Forks	20
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by timscheuerai on GitHub. Read the source before you install it.

Installation

Install the Setup Workspace AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/timscheuerai/linkedin-funnel/tree/main/skills/setup-workspace
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/timscheuerai/linkedin-funnel.git /tmp/linkedin-funnel
mkdir -p .claude/skills
cp -r /tmp/linkedin-funnel/skills/setup-workspace .claude/skills/setup-workspace

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Setup Workspace in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Setup Workspace on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Setup Workspace is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.

Set up the workspace

Read AGENTS.md, README.md, index.md, workspace.example.json and strategy/notion-schema.md. Resolve paths from this skill's repository, not an unrelated current directory.

Local setup

Inspect existing context and local configuration before writing. A populated workspace is not a blank template: preserve its sources, settings and user edits.

Gather the author's name, language, audience, content goal and available source material from the conversation. Ask only for missing choices that affect the requested next step. Time zone, posting days and platform are needed for a dated plan, not for an initial interview.

Create or merge ignored workspace.local.json from the example. Leave unknowns null or empty. Keep credentials in the connected tool's authentication store. This file holds preferences, not evidence for biographical or business claims. Durable decisions go in the relevant context pages with source notes.

Use templates/context-interview.md to start capture. Do not populate identity, proof, voice, hooks or topics with sample answers. No bulk rename is needed to make the generic skills work.

Optional Notion setup

Local drafting works without Notion. Set it up only when included in the request.

Read strategy/notion.local.json if present, otherwise inspect legacy strategy/notion.json if this installation has one. Fetch the configured destination. For a new setup, ask for the parent page or locate the explicitly named one and verify its identity.
Inspect the selected parent's children and existing schemas. Reuse an existing matching setup rather than duplicating it.
Create or map the four databases from strategy/notion-schema.md using the available connector's documented arguments. Store each confirmed ID in strategy/notion.local.json as it is created. Do not copy IDs from the example, another project or an unrelated search result.
Add supported views. If a connector cannot configure a view or native template, report that specific limitation. Do not claim it exists.
Fetch the resulting schemas and query each data source. For a new blank setup, verify all four have no rows. Preserve existing rows when resuming a populated setup.

After any ambiguous write result, inspect the destination before retrying. A database ID and its data source ID may differ.

Optional search and handoff

If search is requested and qmd is installed, run scripts/qmd-setup.sh, then search a known page through scripts/qmd.sh. Otherwise use rg. Do not install packages or embedding models merely to initialize context.

Run scripts/wiki-lint.sh. Report what is connected, what remains blank and the next source to capture. Setup does not schedule content, publish posts or send outreach.

Frequently asked questions

What does the Setup Workspace AI skill do?

Initialize this content workspace for a new author, including local preferences and optional Notion or local search setup.

Why use Setup Workspace on TypingMind?

Because you install it once and use it with any model. Setup Workspace is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Setup Workspace in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/timscheuerai/linkedin-funnel/tree/main/skills/setup-workspace. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Setup Workspace?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Setup Workspace?

As many as you like. As long as a model supports skills, you can use Setup Workspace with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Setup Workspace AI skill free?

Yes. It is published on GitHub by timscheuerai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Discrawl

openclaw

OrganizationPopular

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Notcrawl

Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Set up the workspace

Local setup

Optional Notion setup

Optional search and handoff

Frequently asked questions

Related AI Skills

Set up your own AI workspace now