skilder-ai/skilder

Use when the user wants to make something repeatable for their team in Skilder, such as "turn this into a skill", "save this workflow to Skilder", "make this a role for my team" or "build an App from this". Works from this conversation, a pasted SOP, a transcript, a document or a link. Decides whether the work belongs in skills, a role, an App, or a new version of what the workspace already holds. Suggests tools, or a connector to add, when the work needs one. Creates nothing before the user approves a short summary of what it will build (workspace admin).

Connect this agent to the user's Skilder workspace over MCP with a browser OAuth sign-in. Checks whether Skilder is already connected or already configured by the Skilder plugin, asks once before adding the server to the MCP client configuration, then reports the roles and skills the workspace publishes. Trigger on "connect to Skilder", "set up Skilder", "add the Skilder MCP server".

Use right after Skilder is connected, or when the user asks what Skilder can do, such as "Hey Skilder, get me started", "get started with Skilder", "what's in my Skilder workspace" or "show me around Skilder". Describes the workspace's plugins (roles) in plain language and runs one real first task through the best fit; on a new workspace, offers to import existing skills or set up a first plugin. Not for a user who already named a task (using-skilder).

Use when the user has Agent Skills (SKILL.md folders) on this machine or in this repo and wants them in their Skilder workspace, such as "import my skills to Skilder", "move my local skills into Skilder", "share these skills with my team" or "centralize our agent skills". Scans the usual skill folders, asks once which to import, and creates them as drafts with their files (workspace admin). Not for drafting new capabilities from a conversation or document (capture-work-in-skilder).

Use when the user asks about Skilder Apps, the interactive cards a skill opens in the conversation, such as "list my Skilder Apps", "open the <name> App", "create a Skilder App" or "build a dashboard card for this skill". Lists and opens the workspace's Apps, or designs a first App with the user (its screen and the workspace tools it calls) and builds it after their go (workspace admin).

Use when the user asks what their agent did through Skilder, such as "what did Skilder do", "which skills did that use", "show my Skilder activity" or "why did that Skilder call fail". Reads the session record through the read-only analytics tool and reports the plugins (roles), skills and tools used and how each call ended. Changes nothing.

Use when the Skilder MCP server is connected and the user asks for work a team plugin (role) or skill may cover, such as drafting, reviewing, reporting or running a business process with the workspace's tools. Covers the order of operations (start a session, learn the role, then the skill, then act), the session id every call carries, read versus write tools, files, Apps, feedback, and what each refusal means. Not for connecting Skilder (connect-to-skilder) or first steps (get-started-with-skilder).