SideButton Knowledge Modules

Public-facing publishing guide for SideButton skill packs. The page explains what a skill is for an agentic AI, why anyone would create one, what files live inside a pack (_skill.md, _roles/*.md, *.yaml workflows, skill-pack.json), and walks through a 4-step CLI flow (init → document → validate → publish). It also includes authoring guidelines, a frequently-asked-questions accordion, and a Related links cluster. The page is SEO-targeted at the keyword "agentic AI skill" — title and H1 both lead with that phrase. It is the canonical landing page for prospective pack authors and is reachable from three on-site entry points: footer "Create a skill", homepage "CREATE — Create a skill for agentic AI" CTA, and /skills directory bottom CTA. <title>: Create Skills for Agentic AI — SideButton MCPH1: Create Skills for Agentic AILede: "Author installable skill packs that teach AI coding agents how to operate any web app. Scaffold, validate, and publish in under 30 minutes with the SideButton CLI — free, open-source, and ready to run on Claude Code, OpenAI Codex, Cursor, and every other MCP client." Step 2 also mentions sidebutton install ./your-skill-dir and the local dashboard at http://localhost:9876 for previewing in-progress packs.

The SideButton homepage at sidebutton.com. An 8-section Astro-rendered marketing page positioned around "Open source MCP server for AI coding agents" — an AI agent platform that combines browser automation, a workflow engine, and domain knowledge packs. Works with Claude Code, ChatGPT, Cursor, OpenAI Codex, and any MCP client. The April 2026 redesign dropped the "three layers" framing and embed-buttons focus in favor of an MCP-server-first positioning with a dedicated "Managed AI Teams / Open Source" CTA section that integrates customer testimonials. As of the late-April 2026 iteration the header nav was reshuffled (Knowledge Packs renamed to "Skills", "MCP Server" added), the Compatibility section now contains 5 directly-linked client cards (Claude Code, OpenAI Codex, ChatGPT, Cursor, +Any MCP client) routing to /mcp/{client}, and a new "Use or create agentic AI skills" section was inserted between Knowledge Packs and Community Roles. The page surfaces 6 featured knowledge packs and a 10-row role-playbook grid linking into /skills/{pack}/roles/{role} pages. Note: /demo no longer exists — navigating there redirects to /. <title>: SideButton MCP Server. AI Agent Platform Workflow Automation Navigation change late-Apr 2026: Nav now reads: MCP Server | Skills | Media | Docs | Book a Demo | GitHub. "Knowledge Packs" was renamed to "Skills"; "MCP Server" was added as a new top-level item. Mobile menu link order: Book a Demo, MCP Server, Skills, Media, Docs, GitHub. Role URL pattern: /skills/{pack-slug}/roles/{role-slug} (e.g., /skills/agents/roles/se, /skills/github/roles/se). Total on site: 16 knowledge packs (homepage CTA reads "Browse all 16 knowledge packs →").

The Knowledge Packs directory at /skills is the public-facing catalog of installable knowledge packs ("skills") for SideButton AI agents. As of late-April 2026 it shows one flat list of 16 available packs with two side-by-side CTA cards (USE / CREATE) at the top, a client-side search input below, and a "Missing a skill for your app?" footer block. The module also covers two sub-routes: /skills/{slug} — pack detail pages that render the full installed pack content (H1 = {Pack Name} Skill for MCP Agent, then the pack's _skill.md tree). Includes Copy install command button, Download ZIP link, in-page table-of-contents nav, and a sticky right-side complementary sidebar with source/docs/coverage links./skills/{slug}/roles/{role} — role playbook pages that render an individual role file from a pack (H1 = {Role Display Name} — {Pack Name} Role Playbook). Includes the same install + download buttons, breadcrumb nav, and bottom links to siblings (← All {Pack} roles, {Pack} overview). No authentication required for any /skills* route. No query params observed — search state is purely client-side (not reflected in URL). ⚠️ Old "Publish knowledge packs for free" banner with sidebutton init / sidebutton publish code blocks has been REMOVED. Tests that snapshot for those code blocks will fail. ⚠️ The sidebutton pack module count dropped from 21 to 13 — the published pack has been re-scoped vs older verifications. Don't assert a constant module count.

Four static legal pages plus two redirected-away paths. Pages share the Astro marketing Layout with Header + Footer and follow an identical pattern: centered prose content (max-w-3xl) under an H1 heading with a "Last updated" or descriptive subtitle. Content is pure text with H2/H3 subsections, tables, lists, and mailto/external links. No interactive elements beyond navigation and standard anchor links. Current coverage: privacy, terms, content-policy, imprint. The DMCA and Trademarks pages have been removed — /dmca and /trademarks now 301-redirect to /. Verified 2026-04-20: curl HEAD returns 200 for /privacy, /terms, /content-policy, /imprint; 301 (Location: /) for /dmca and /trademarks. All remaining 4 pages share this exact layout — only the <title>, H1, subtitle, and .prose-content body differ. As of 2026-04 the footer exposes Privacy | Terms | Content Policy | Imprint — DMCA and Trademarks have been removed from the footer. Static prose content — no editable entities or form fields on any legal page. Previously documented as a 5-tier escalation table (Warning → Permanent ban). Detail verification TODO — re-read full page body if precise table rows are needed. Previously documented: 3 tables (data collection / retention / cookies) + a 4-item summary grid at bottom. Detail verification TODO — structure appears unchanged based on section headings. 1. Navigate between all remaining legal pages /privacy — verify H1 "SideButton Privacy Policy"/terms — verify H1 "SideButton Terms of Service"/content-policy — verify H1 "SideButton Content Policy"/imprint — verify H1 "SideButton Legal Notice (Imprint)" 2. Verify redirected legal paths

Public-facing news and releases page added in the April 2026 redesign. Serves as a press/news index that links to individual announcement posts. Each post is rendered from a static MDX/markdown file at build time. Reachable from the header nav (replaced "Contribute" in the header) and the footer. As of 2026-04-26 the index lists one post: the platform launch announcement at /media/sidebutton-open-source-platform-release. <title>: SideButton News & ReleasesH1: SideButton News & ReleasesCanonical: https://sidebutton.com/mediaMeta description: News, releases, and updates from SideButton — the open-source MCP server and AI agent platform.og:title: same as <title>; og:image: /og-image.png (site-wide default) The post image alt text and the H2 are identical, so link "SideButton — Open Source Platform for AI Agents" and img "SideButton — Open Source Platform for AI Agents" and heading "SideButton — Open Source Platform for AI Agents" all match the same post. Use the heading/H2 role for the title, the img role for the hero, and grab the wrapping link for navigation. Verified against /media/sidebutton-open-source-platform-release on 2026-04-26. <title>: post-specific (e.g. SideButton — Open Source AI Agent Platform) — note the title is slightly different from the index card heading (the index uses "Open Source Platform for AI Agents", the post uses "Open Source AI Agent Platform")H1: matches <title> (post title)Canonical: https://sidebutton.com/media/{slug}og:type: website (not article — post detail pages do not use article-typed OG)<time>: <time datetime="2026-04-12" class="text-sm text-text-muted">April 12, 2026</time> inside a div Post count as of 2026-04-26: 1. 1. Reach the media index From any page, click header link "Media" OR footer link "Media" → /media

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file. VERIFIED 2026-04-20: Page structure confirmed against live fleet (12 agents observed: typical fleet has ~1 sidebutton-owned agent + N tenant-owned agents). Top actions: button "Share" + button "Run Workflow". H1: "Agent Fleet". Each card shows screenshot, Copy hostname + Copy IP buttons, CPU/Memory/Load/Disk/Swap spans, Queue + Jobs links, Refresh agent data button, Run Job button (may be disabled per-agent). Auth0 login required; sidebar nav now includes Automations (see portal-chat skill for sidebar details). Page title: "Agents - SideButton Fleet".

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file. VERIFIED 2026-04-20: H1 "Automations". Top control: button "+ New Automation" opens modal (H3 "New Automation") with title input ("My automation" placeholder), priority buttons (Max / High / Medium), Cancel / Save. Delete confirm modal has H2 "Delete Automation" + Cancel / Delete. Automation rows link to /portal/automations/{id}, with "N jobs" link → /portal/queue?automation_id={id} and inline edit link → /portal/automations/{id}/edit. Names follow pattern {source}>{state} >> {action} - A{id} or {source}>{state}>{action} — {source} is JIRA, home, or another trigger source; {id} is the automation numeric id. Auth0 login required. Workflow trigger automation page -- allows creating automations that automatically dispatch workflow jobs to agents based on events from Jira, SideButton, or a cron schedule. Each automation has a WHEN trigger configuration and a WHAT action configuration (workflow, agent, effort level). Automations can be enabled/disabled via toggle switches, manually triggered, and show dispatch count badges linking to the queue. The page lists all automations with their trigger type, workflow label, and action buttons.

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file. SOURCE OF THIS FILE (2026-09-03): written from the shipped implementation, with route behaviour confirmed unauthenticated. Everything below marked (source) comes from the repo rather than from a browser pass; re-verify it logged in before raising confidence. The account's capability sheet: what can this fleet actually do, in six server-rendered tabs — Roles · Workflows · Playbooks · Skills · Workspace · Agents. It is the hub of the sidebar's Settings level and the home of the per-agent role and effort controls. Three older pages became tabs of it and stay reachable as deep pages (/portal/roles, /portal/workflows, /portal/skills). Its design rule is data honesty: the page never merges what the portal asked for with what an agent reported, and it never invents an answer it does not have. That is why a delivery field says who stamped it, a declared-but-unrouted workflow verdict says so, and the two workspace-shaped tabs refuse to answer at all under All workspaces.

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file. AUTH0 MIGRATION (2026-04-20): Portal auth uses Auth0 Universal Login at sidebutton.eu.auth0.com/u/login. Unauthenticated requests 302-redirect through /portal/login → Auth0. Log-out URL is now /api/auth/logout (Auth0 logout endpoint). Chat interface for Fleet Control -- the default landing page of the authenticated portal. A three-panel layout: left sidebar (Fleet Control navigation), middle panel (conversation history list with "+ New Chat" button and search bar), and right panel (active conversation messages or empty state). Users chat with an AI assistant that can run workflows on agents, queue dispatch jobs, list available workflows, list agents, and answer questions. The assistant renders markdown in responses (bold text, inline code, numbered/bullet lists, paragraphs). The portal redirects /portal to /portal/chat automatically. Change 2026-04-20: The user avatar + email row at the sidebar bottom has been REMOVED. The sidebar now shows only nav links + "Log out" — no account info block. The chat assistant can perform these actions based on natural language input: 1. Start a new chat

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file.

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file. VERIFIED 2026-04-20: H1 "Dispatch Queue". Top control: button "+ Add Item" opens heading "Add to Queue" modal with ticket input (placeholder "SCRUM-42 or https://...atlassian.net/browse/SCRUM-42") + extras textarea ("Extra instructions for the agent…") + button "Add to Queue" (submit). Queue items have button "Retry" and button "Resend" actions. Search input: textbox "Search tickets…". Auth0 login required. Dispatch Queue page -- a work queue for scheduling workflow jobs to be dispatched to agents. Items can be added manually via the "+ Add Item" form, by pasting batch Jira tickets in Chat, or automatically via Automations. Each queue item specifies a workflow, optional agent assignment, ticket URL/key, effort level, and optional hint. Items progress through states: Waiting (10s delay) -> Queued -> Dispatching -> Dispatched -> Completed, or Failed/Cancelled. The page has filter tabs, search, workflow/agent filter dropdowns, and an inline "Add to Queue" form panel.

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file. RETIRED 2026-09-03 (KAN-56) — Agents tab: the per-agent role checkboxes and the per-agent effort dropdown are no longer on this page. Both moved to Capabilities → Agents (/portal/capabilities/agents), and the tab's own description now reads "Manage agent workspaces and environment config…. Roles and effort moved to Capabilities → Agents" with an orange link there. What the panel keeps: avatar, rename, status, RDP/SSH, workspace assignment, agent env, reboot/delete. Do not look for a role toggle here — see skill://sidebutton.com/portal-capabilities/_skill.md. The account-level effort tier pills in General (#effort-pills) are a different control and are unaffected.

PRIVACY CONVENTION: This skill file must describe the PAGE — elements, selectors, layouts, states, and public UI copy (placeholder text, button labels, default headings). It must NOT record tenant-specific data visible to a logged-in user: real ticket keys (use PROJ-123), real agent hostnames (use agent-host or {hostname}), real IP addresses (use 203.0.113.10), real workflow/automation IDs (use {id}), real user names or emails, real Jira host (use {tenant}.atlassian.net), real registry names (use {registry-name}), or real automation display names. When re-verifying, generalize observed values before writing them into this file. NAV LOCATION CHANGED 2026-09-03 (KAN-56): Workflows is no longer its own sidebar item. It is a deep page of Capabilities → Workflows — reach it from /portal/capabilities/workflows (the tab's Workflows page button) or by URL; the header carries a ← Back to Capabilities link, and the sidebar lights the Capabilities → Workflows sub-item, not a top-level Workflows item. The tab, not this page, is where a workflow's effort / app / enabled are edited and where Run now opens the run modal. Page content below is unchanged. Sibling module: skill://sidebutton.com/portal-capabilities/_skill.md.

Portal authentication entry point. As of the April 2026 redesign, SideButton switched from a custom email-only login form to Auth0 Universal Login. Users arriving at /login or /portal/login are 3xx-redirected to the hosted Auth0 login page at sidebutton.eu.auth0.com/u/login. The Auth0 page presents a standard email + password form with a "Show password" toggle and "Reset password" link. Successful authentication redirects back to the SideButton portal. Verified 2026-04-20 via curl. <title>: Log in | SideButtonHost: sidebutton.eu.auth0.comPath: /u/login User navigates to /login → 308 → /portal/login/portal/login (server-side) → 302 → Auth0 hosted page with ?state=<opaque-token>User submits email + password → Auth0 validatesOn success: Auth0 redirects back to SideButton callback URL with session tokenSideButton server sets session cookie → user lands on /portal/chat 1. Log in to the portal Navigate to /login OR /portal/login OR any /portal/* route while unauthenticatedGet redirected to sidebutton.eu.auth0.com/u/loginFill textbox "Email address *"Fill textbox "Password *"Click button "Continue"On success: redirect back to /portal/chat 2. Reset forgotten password On Auth0 login page, click link "Reset password"Follow Auth0's password-reset flow 3. Toggle password visibility while typing Click switch "Show password" to reveal plain textClick again to re-mask