SkillCDN 콘솔
SkillCDN 콘솔(조직이 AI 에이전트와 일을 돌리는 보드)의 스킬: 에이전트가 console 명령으로 보드의 작업을 하는 법, @skillcdn/console 패키지로 개인 콘솔이나 조직 콘솔을 만드는 법, 그리고 조직의 콘솔을 AWS와 Cloudflare에 1인부터 100인 규모까지 배포하는 법. 콘솔의 문서(아키텍처, 결정 기록, REST API와 명령줄의 명세)도 함께 제공합니다.
https://skillcdn.ai/gh/skillcdn/console내 AI에 이 주소를 연결하면 이 스킬들을 쓸 수 있어요. 연결 방법 보기
- 저장소
skillcdn/console - 기본 브랜치
main - 커밋
3ca3d30 - 라이선스
MIT
저장소 둘러보기
스킬과 문서의 원문에서 찾습니다. 화면용 번역은 검색되지 않아요.
One short file per decision that has lasting consequences and that a future contributor might reasonably want to undo: a dependency the system is built around, a boundary between workspaces, a data-m…
문서
- ADR-0001: The console is the reference console, built on the published packagesSkillCDN turns a git repository into an MCP server; its specification, server and web UI live in the main repository, skillcdn/skillcdn. The maintainers want a console: where an organization runs its…docs/adr/0001-the-console-is-the-reference-console-built-on-the-published-packages.md
- ADR-0002: One image, one database, and the main repository's toolchain and conventionsThe console will run in two places from the start: on a developer's machine, and on a cloud for the organization that uses it. Later it will run for other organizations, from their own installations.…docs/adr/0002-one-image-one-database-and-the-main-repositorys-toolchain.md
- ADR-0003: The console is licensed under MITThe main repository is source-available under FSL-1.1-ALv2, which reserves one thing: offering SkillCDN itself as a competing commercial service. That reservation protects the product. The console is…docs/adr/0003-the-console-is-licensed-under-mit.md
- ADR-0004: People and agents reach the board only through the API, each with a credential of their ownThe board is shared by several people and by the agents working for them, and the console must say on every request who is asking and what they may do. Two ways were open: let each person and agent h…docs/adr/0004-people-and-agents-reach-the-board-only-through-the-api-with-a-credential-of-their-own.md
- ADR-0005: People sign in through an identity provider; membership and roles are the console's ownThe console keeps no passwords. People sign in through an account they already have: GitHub first, since that is where the organization's repositories and the agents' pull requests are. The organizat…docs/adr/0005-people-sign-in-through-an-identity-provider-and-membership-and-roles-are-the-consoles-own.md
- ADR-0006: Agents work the board through the REST API and the command line, not through an MCP serverThe second milestone first connected agents to the console as an MCP server: a set of tools over Streamable HTTP, which the agents people run (Claude Code, Codex) speak without anything installed. Bu…docs/adr/0006-agents-work-the-board-through-the-rest-api-and-the-command-line-not-an-mcp-server.md
- ADR-0007: The package is published through trusted publishing, and its version follows the `@skillcdn/core` line it is built onThe console has one versioned artifact: @skillcdn/console, which a machine installs to get the console command and a team builds a custom console from. The image has no version of its own; a deployme…docs/adr/0007-the-package-is-published-through-trusted-publishing-and-versioned-on-the-core-line.md
- ADR-0008: A workspace holds projects, and what a person may see and change is decided per projectThe board was one: every task, run and decision of the workspace, seen and changed by every member. An organization runs several efforts at once, each with its own people, its own playbooks and skill…docs/adr/0008-a-workspace-holds-projects-and-what-a-person-may-see-and-change-is-decided-per-project.md
- ADR-0009: Documents are pages of Markdown in a project, addressed by path, versioned, and linked both waysThe board holds what is to be done and what was decided; the knowledge the work rests on, playbooks, designs, notes, findings, has no place of its own and lives in conversations, in agents' memories…docs/adr/0009-documents-are-pages-of-markdown-in-a-project-addressed-by-path-versioned-and-linked-both-ways.md
- ADR-0010: The default UI's addresses name what they show, and every page and form has oneThe default UI routed a project's pages under /p/<key>, a letter that says nothing and that the REST API does not use. The forms (a new project, a new task, a decision raised, a page written or edite…docs/adr/0010-the-default-uis-addresses-name-what-they-show-and-every-page-and-form-has-one.md
- ADR-0011: An agent connects with a short code a person approves, and the token is never shownUntil now a person connected their agent by making a token on their own page, copying it, and pasting it where the agent runs: a secret shown on a screen, carried through a clipboard, sometimes throu…docs/adr/0011-an-agent-connects-with-a-short-code-a-person-approves-and-the-token-is-never-shown.md
- ADR-0012: The pages speak the person's language, from packs that ship with the packageEverything committed to this repository is in English, with one exception allowed from the start (AGENTS.md, rule 10): what people read in their own language, once the UI gets language packs. Milesto…docs/adr/0012-the-pages-speak-the-persons-language-from-packs-that-ship-with-the-package.md
- ADR-0013: The default brand comes from a published package of the main repository, through a slot in the consoleThe default console shows the workspace's name and nothing else of who makes it. Milestone 5 of the roadmap asks for SkillCDN's favicon, symbol and wordmark in the default console, from a published p…docs/adr/0013-the-default-brand-comes-from-a-published-package-of-the-main-repository-through-a-slot-in-the-console.md
- ADR-0014: A person's own console is served from their machine by the command, with the token it keepsThe package is meant for two kinds of custom console (architecture.md): the organization's, which replaces the default UI the image serves, and a person's own, which a member builds from the package…docs/adr/0014-a-persons-own-console-is-served-from-their-machine-by-the-command.md
- ADR-0015: The console's skills live in this repository in the SkillCDN Format, and the package carries them with its sourcesTwo kinds of agent meet the console: one working a task on the board through the command, and one building a console of a person's own, or an organization's, from the package (ADR-0014). Both need to…docs/adr/0015-the-consoles-skills-live-in-this-repository-in-the-skillcdn-format-and-the-package-carries-them.md
- ADR-0016: The bucket is reached through the S3 API with the console's own signing, on one pair of keys, and reads what the rows kept before itThe files runs hand in and people attach to documents are kept behind the blob-store port, in rows of PostgreSQL so that the smallest install has one dependency (ADR-0002). On a cloud the bytes belon…docs/adr/0016-the-bucket-is-reached-through-the-s3-api-with-the-consoles-own-signing-and-reads-what-the-rows-kept-before-it.md
- ADR-0017: The reference deployment is the image on AWS behind Cloudflare, written as a skill, and the code stays cloud-neutralMilestone 8 of the roadmap ends with the console deployed next to a managed PostgreSQL and a bucket. ADR-0002 keeps the cloud out of the code, and deploy/README.md says what a platform must provide;…docs/adr/0017-the-reference-deployment-is-the-image-on-aws-behind-cloudflare-written-as-a-skill.md
- ADR-0018: The bucket may be reached with the credentials the platform hands the container, through a port of their ownADR-0016 reaches the bucket with the console's own signing on one pair of keys from configuration, and left open reading the credentials a platform hands a container itself. The first deployment of t…docs/adr/0018-the-bucket-may-be-reached-with-the-credentials-the-platform-hands-the-container.md
- Architecture Decision RecordsOne short file per decision that has lasting consequences and that a future contributor might reasonably want to undo: a dependency the system is built around, a boundary between workspaces, a data-m…docs/adr/README.md