Registry · Clearance PUBLIC
Approved SI Modules
Skills cleared as Super Intelligence modules; multi-step packages ship as SI Intelligences. Copy a session prompt into your Super Intelligence — connect via MCP, or use discovery at /.well-known/agent-skills/. Restricted clearance: /private.
Protocol · Streamable HTTP
Super Intelligence MCP
Point your Super Intelligence at the Ministry's Model Context Protocol endpoint. Server name 1node-si. Endpoint: https://1node.si/mcp.
Public tools are open. Restricted clearance tools require authorization on the same endpoint.
Tools
- list_skills
- get_skill
- list_skill_files
- get_skill_file
- list_agents
Client config
{
"mcpServers": {
"1node-si": {
"url": "https://1node.si/mcp"
}
}
}Azure Pipelines for Docker image build, Amazon ECR push, and ECS service update using parameterized environments, DownloadSecureFile for .env, Docker@2, ECRPushImage@1, and AWSCLI@1. Documents duplicate push tasks when tasks require literal AWS regions. Use for ADO-to-AWS container deploy flows.
Azure Pipelines deploy to Azure Static Web Apps using AzureStaticWebApp@0 with pre-built artifacts, skip_app_build, environment-scoped deployment tokens, and stage conditions on branches or tags. Documents staticwebapp.config.json and navigationFallback for SPA routers (Vue/React). Use after ado-nodejs-build publishes a dist folder.
Azure Pipelines deployment to App Service using AzureRmWebAppDeployment@4: PublishProfile + password secret, or Azure Resource Manager service connection with packageForLinux and StartupCommand for Linux .NET. Covers deployment jobs, environments, and optional SetParameters.xml overrides. Use when wiring ADO stages after DotNetCoreCLI publish artifacts.
Azure Pipelines .NET CI using DotNetCoreCLI@2 for restore, build, and publish, plus PublishBuildArtifacts@1. Covers Linux zip publish, Windows MSDeploy web package patterns, optional extra artifacts (publish profiles), and variable groups with local csproj/sln paths. Use when authoring ADO YAML for .NET before git deploy, Azure Web App deployment, or manual release.
- ado-nodejs-buildskill
Azure Pipelines Node.js builds using NodeTool@0, npm or yarn scripts, Cache@2 for npm, branch- or parameter-driven env vars (e.g. VITE_* from variable groups), and PublishBuildArtifacts@1 for dist folders. Use when authoring ADO YAML for frontends before Static Web Apps, App Service static content, or embedding into .NET publishes.
- agents-md-syncskill
Requires updating AGENTS.md when general skills, conventions, or cross-cutting agent patterns change in a repository. Use when editing agent configuration, adding or changing project skills (e.g. under .cursor/skills/ or .agents/skills/), or changing repo-wide agent workflows that other agents should assume.
Designs Azure Pipelines CD that syncs build artifacts into a dedicated Git deployment repository, commits, and pushes so a server-side Git hook runs deploy. Covers build-stage ZIPs (ExtractFiles@1), Linux (rsync) and Windows (robocopy /MIR) agents, CmdLine tasks, and required variables. Use when implementing Azure DevOps CD, git push deploy, post-receive hooks, or mirroring artifacts into a deploy repo.
Designs GitHub Actions CD that mirrors build output into a dedicated Git deployment repository, commits, and pushes so a server-side Git hook runs deploy. Supports Linux (rsync) and Windows (robocopy /MIR). Emphasizes optional deploy steps in the same job as the build so free accounts avoid upload-artifact storage; documents a separate-job pattern when needed. Use when implementing GitHub Actions CD, git push deploy, post-receive hooks, or mirroring build output into a deploy repo. Covers hosted and self-hosted Linux runners and optional compact single-step deploy scripts.
Cross-cutting CI/CD conventions: Linux-first runners when the stack allows it, explicit step identifiers, deployment environments, Azure Pipelines stages and variable groups, and GitHub Actions environments. Use when authoring or reviewing pipelines, choosing agents, or structuring build vs deploy for Azure DevOps or GitHub Actions.
GitHub Actions for Docker build and push to Amazon ECR with OIDC (configure-aws-credentials, amazon-ecr-login, docker/build-push-action) and optional ECS deploy (amazon-ecs-render-task-definition, amazon-ecs-deploy-task-definition). Covers date-stamped tags plus latest or latest-dev. Use for GHA container pipelines to AWS ECR/ECS.
Configures GitHub Actions deployment to Azure App Service (Web Apps) using the official azure/webapps-deploy action—publish-profile or Azure Login (service principal), package paths, slots, and containers. Use when adding or updating Azure Web App deploy steps, App Service CI/CD, or migrating from Azure DevOps deploy to GitHub Actions.
Defines date-based build versions in GitHub Actions using bash date stamps and GITHUB_OUTPUT, with optional suffixes for environment (e.g. -dev). Use when tagging artifacts, docker images, git deploy commits, or release metadata without CalVer from the repo.
Builds .NET projects in GitHub Actions using actions/setup-dotnet with a standard restore → build → publish pipeline, output under an artifacts folder, and optional dotnet test when tests are requested or test projects exist. Use when authoring or fixing GitHub workflows for .NET, SDK pinning, or CI before deploy (e.g. Azure Web App package layout).
Builds Node.js frontends or packages in GitHub Actions using actions/setup-node, npm or yarn installs, and working-directory for monorepo apps. Defaults Node to latest LTS unless package.json engines or the user pins a version. Use when authoring Node CI, frontend builds, or combining multiple JS packages in one job.
Good-enough Pimcore production on a bare Ubuntu VPS — not a polished platform, just a workable Compose + Traefik/MariaDB host with hardening (SSH/fail2ban/UFW), deploy user pimcore + pimcore-ctl, shared/.env, GitHub Actions SSH deploy, product registration, one-time pimcore-install, and go-live checks. Use when standing up a new Pimcore project on a VPS or you need a pragmatic host stack and accept the sharp edges. Reference pack and host scripts live in this skill.
Audits GitHub Actions workflow files for outdated `uses:` references, resolves current major (or latest) tags from each action’s repository, and updates YAML to match—fixing stale pins like actions/checkout@v4 when v6 is current. Use when refreshing workflows, after copying samples from docs, or when the user asks to bump GitHub Actions versions.
Designs, authors, and refactors Azure Pipelines YAML (azure-pipelines.yml or multi-file pipelines): stages, templates, parameters, deployment jobs, environments, variable groups, and marketplace tasks. Use when the user asks for ADO CI/CD, .NET or Node builds, Azure Web App or Static Web Apps deploy, Docker/ECR/ECS to AWS, or git-push CD from Azure Pipelines. Prefer this agent when the deliverable is production-ready Azure Pipelines YAML.
Designs, authors, and refactors GitHub Actions workflows (.github/workflows/*.yml). Use when the user asks for CI/CD on GitHub, workflow YAML, reusable actions, runners, environments, secrets vs OIDC, or stacks that combine build (Node/.NET), deploy (Azure Web App, git-push CD, AWS ECR/ECS), and date-based image or artifact versioning. Prefer this agent over generic chat when the deliverable is production-ready workflow YAML.