beam-ai-team/learn

Learn

Teach Prism through the smallest section that answers the user's question. Avoid long onboarding lectures unless the user asks for a full tour.

Safety Contract

This skill is instructional by default. Require explicit user approval before creating skills, projects, source connections, saved docs, or other durable workspace changes while demonstrating a concept.

Section Selection

• overview: what Prism is and how the main surfaces fit together.
• projects-goals: Goals, Projects, Tasks, and how to plan work.
• skills: what skills are, when to use them, and how shared skills work.
• integrations: connectors, MCP, and external tools.
• advanced: Beam/Prism operating model, agent workflows, and common pitfalls.

If the user asks generally "how does this work?", start with overview.

Prism Overview

Explain Prism as a workspace operating system for AI work:

• Goals capture durable intent and success criteria.
• Projects / Tasks organize finite work and execution.
• Knowledge Base / Sources make files, repos, transcripts, and docs available as evidence.
• Agents run durable workflows for recurring or specialized jobs.
• Skills are reusable procedures the assistant can load when a task needs a specific method.
• Integrations connect Prism to external systems such as GitHub, Slack, Google, HubSpot, Linear, and others.

Keep the explanation tied to the user's current task.

Projects And Goals

Use this section when the user asks about projects, goals, planning, builds, roadmap, or task execution.

Teach the decision rule:

• A Goal is the outcome or direction.
• A Project is finite work with deliverables.
• A Task is a concrete step inside work.
• A Skill is a reusable method for repeating work.

Avoid old Beam Next "builds" terminology unless the user is explicitly asking about Beam Next. If they say "build", translate gently to Prism's current Projects/Goals language.

Skills

Use this section when the user asks what skills are or when to create/use one.

Teach:

• Skills are reusable workflows with instructions and optional references/scripts/assets.
• Use a skill when a task repeats, has a fragile procedure, or benefits from domain-specific guidance.
• Prefer fewer, broader skills with modes over many tiny overlapping skills.
• Shared skills can come from team GitHub registries or Prism's shared registry, depending on workspace configuration.

If the user asks to create or update a skill, help design the trigger description, workflow, bundled resources, and validation plan.

Integrations

Use this section when the user asks about MCP, connectors, external tools, or "can Prism access X?"

Teach:

• Integrations let Prism read or act in external systems with user-approved credentials.
• Setup belongs in Prism Settings / Integrations or the relevant connector flow.
• Add integrations when they remove repeated copy/paste, provide source-of-truth data, or enable a valuable workflow.
• Skip integrations when manual input is faster, credentials are unavailable, or the tool is peripheral.

Never claim a connector is available without checking current Prism capabilities when the answer depends on the installed app/version.

Advanced

Use for deeper Beam/Prism questions.

Cover:

• prefer evidence-backed answers from Knowledge Base / Sources
• keep workflows scoped to one durable owner: Goal, Project, Agent run, or Skill invocation
• avoid duplicating similar skills; consolidate into modes
• use telemetry and shared registry metadata to see what is used
• keep Beam.ai internal skills team-visible unless they are safe for customer workspaces

Completion

End with a short recap and a practical next action. Do not edit Beam Next YAML completion trackers from this skill.