LangBot EBA Adapter Development
langbot-app/LangBot
Guides building, migrating and testing LangBot messaging-platform adapters for the Event-Based Agents layout, with unified event and message conversion.
Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.
Install Writing Workspace Signals
$ npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install friday-platform/friday-studio writing-workspace-signals --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system/skills/writing-workspace-signals .claude/skills/writing-workspace-signals && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-workspace-signals" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/writing-workspace-signals into .claude/skills/writing-workspace-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-workspace-signals", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/writing-workspace-signalsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install friday-platform/friday-studio writing-workspace-signals --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system/skills/writing-workspace-signals .agents/skills/writing-workspace-signals && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-workspace-signals" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/writing-workspace-signals into .agents/skills/writing-workspace-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-workspace-signals", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install friday-platform/friday-studio writing-workspace-signals --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system/skills/writing-workspace-signals .cursor/skills/writing-workspace-signals && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-workspace-signals" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/writing-workspace-signals into .cursor/skills/writing-workspace-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-workspace-signals", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/friday-platform/friday-studio.git --path packages/system/skills/writing-workspace-signals--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install friday-platform/friday-studio writing-workspace-signals --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system/skills/writing-workspace-signals .gemini/skills/writing-workspace-signals && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-workspace-signals" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/writing-workspace-signals into .gemini/skills/writing-workspace-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-workspace-signals", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install friday-platform/friday-studio writing-workspace-signalsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system/skills/writing-workspace-signals .github/skills/writing-workspace-signals && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-workspace-signals" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/writing-workspace-signals into .github/skills/writing-workspace-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-workspace-signals", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install friday-platform/friday-studio writing-workspace-signals --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system/skills/writing-workspace-signals .opencode/skills/writing-workspace-signals && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-workspace-signals" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/writing-workspace-signals into .opencode/skills/writing-workspace-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-workspace-signals", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-workspace-signals- GitHub stars
- 104
- Token cost
- ~2.1k tokens
- SKILL.md length
- 821 words
- Files
- 4 (incl. assets)
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.
- Editing signals in workspace.yml
- SKILL.md covers Checklist, Two foot-guns, Wiring HTTP signals to… and Templates, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A signal needs to accept user input from the Run dialog
What it does
Writing Workspace Signals is an agent skill from friday-platform/friday-studio. Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring. Use when creating or editing signals in workspace.yml; when a signal needs to accept user input from the Run dialog; or when signal validation or runtime dispatch fails.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including assets (for example `assets/http-signal-with-schema.yml`, `assets/minimal-http-signal.yml` and `assets/schedule-signal.yml`).
It sits in Backend & APIs. The repository describes itself as: Agent Harness Platform — shareable workspaces, MCP tools, skills, memory, and cron/webhook automations. Self-hosted and transparent.
When your agent uses it
- Editing signals in workspace.yml
- A signal needs to accept user input from the Run dialog
- Signal validation
- Runtime dispatch fails
Example prompts
- “Use the writing-workspace-signals skill to author Friday workspace signals with correct provider configs, payload schemas, and runtime wiring”
- “/writing-workspace-signals”
What it can do on your machine
Read from SKILL.md and the folder at commit fb3069a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Workspace Signals loads about 2.1k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 821 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 821 words (~2,108 tokens).
“No schema → Run dialog renders no input fields → payload arrives empty. Job gets {} instead of the params it expects.”
- name
- writing-workspace-signals
Files
SKILL.md and 3 other files (assets) in packages/system/skills/writing-workspace-signals of friday-platform/friday-studio.
- SKILL.md
- assets/http-signal-with-schema.yml
- assets/minimal-http-signal.yml
- assets/schedule-signal.yml
Open the folder on GitHubat commit fb3069a
Compare with similar skills
Writing Workspace Signals next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Workspace Signals this skillfriday-platform/friday-studio | 104 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| LangBot EBA Adapter Developmentlangbot-app/LangBot | 18k | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Wp Performancegambitph/Stackable | 351 | 3 repos | ~1.5k | Automated safety check: Pass | GPL-3.0 | |
| Trigger.dev Background Taskspapermark/papermark | 9.2k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Flow Nexus Swarmruvnet/agentic-flow | 817 | 4 repos | ~4.2k | Automated safety check: Pass | None | |
| Integrate Whatsappgokapso/agent-skills | 177 | — | ~4.8k | Automated safety check: Pass | None |
Similar skills
Wp Performance
gambitph/Stackable
A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…
Trigger.dev Background Tasks
papermark/papermark
Guides building durable background tasks, scheduled jobs and queues with Trigger.dev, including retries, waits, idempotency and concurrency limits.
Flow Nexus Swarm
ruvnet/agentic-flow
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform
Integrate Whatsapp
gokapso/agent-skills
Connect WhatsApp to your product with Kapso: onboard customers with setup links, detect connections, receive events via webhooks, and send messages/templates/media.
Email Deliverability Audit
growthenginenowoslawski/coldoutboundskills
Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.
More from friday-platform/friday-studio
All 20 skills in this repoAuthoring Skills
friday-platform/friday-studio
Authors new agent skills that follow the Anthropic + agentskills.io specification.
Friday CLI
friday-platform/friday-studio
Interacts with a running Friday daemon via CLI and HTTP — lists/creates/modifies workspaces, triggers signals, watches sessions, publishes skills and agents.
Workspace API
friday-platform/friday-studio
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.
Composing Emails
friday-platform/friday-studio
General styling and tone guidelines for composing HTML emails.
Repairing Workspaces Agents
friday-platform/friday-studio
Repairs and upgrades existing Friday workspaces, jobs, user agents, and generated agents to current runtime contracts.
Using Elicitations
friday-platform/friday-studio
Asks the user mid-run from inside an FSM action or Python type: user agent via the elicitation tools — requesttoolaccess for allowlist approvals and requesthumaninput for HITL (human-in-the-loop)…
Related
Categories
Questions about Writing Workspace Signals
What does Writing Workspace Signals do?
Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring. Writing Workspace Signals is an agent skill from friday-platform/friday-studio. Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.
When should I use Writing Workspace Signals?
Writing Workspace Signals fits situations like: editing signals in workspace.yml; A signal needs to accept user input from the Run dialog; signal validation; runtime dispatch fails.
How do I install Writing Workspace Signals in Claude Code?
Run `npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a claude-code`. Or copy the skill folder (packages/system/skills/writing-workspace-signals in friday-platform/friday-studio) into .claude/skills/writing-workspace-signals in your project. Claude Code loads it when a task matches its description.
How do I install Writing Workspace Signals in Codex?
Run `npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a codex`. Or copy the skill folder (packages/system/skills/writing-workspace-signals in friday-platform/friday-studio) into .agents/skills/writing-workspace-signals in your project. Codex loads it when a task matches its description.
Can I use Writing Workspace Signals in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add friday-platform/friday-studio --skill writing-workspace-signals -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-workspace-signals, .gemini/skills/writing-workspace-signals, .github/skills/writing-workspace-signals and .opencode/skills/writing-workspace-signals in your project.
What does Writing Workspace Signals need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Workspace Signals is instructions for the agent only.
Does Writing Workspace Signals access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Workspace Signals safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Writing Workspace Signals use?
Writing Workspace Signals has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Writing Workspace Signals use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Writing Workspace Signals?
Skills that share tags, products or a category with Writing Workspace Signals: LangBot EBA Adapter Development (langbot-app/LangBot, 18k stars), Wp Performance (gambitph/Stackable, 351 stars), Trigger.dev Background Tasks (papermark/papermark, 9.2k stars) and Flow Nexus Swarm (ruvnet/agentic-flow, 817 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Workspace Signals?
friday-platform (a GitHub organization) maintains it in friday-platform/friday-studio, which has 104 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 5, 2026.
Source: friday-platform/friday-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.