Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Deploy memorains to production servers. An agent skill from redTreeOnWall/memorains.
Install Memorains Deploy
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add redTreeOnWall/memorains --skill memorains-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install redTreeOnWall/memorains memorains-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/memorains-deploy .claude/skills/memorains-deploy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "memorains-deploy" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-deploy into .claude/skills/memorains-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-deploy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-deployType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add redTreeOnWall/memorains --skill memorains-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install redTreeOnWall/memorains memorains-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/memorains-deploy .agents/skills/memorains-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memorains-deploy" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-deploy into .agents/skills/memorains-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-deploy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add redTreeOnWall/memorains --skill memorains-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install redTreeOnWall/memorains memorains-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/memorains-deploy .cursor/skills/memorains-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memorains-deploy" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-deploy into .cursor/skills/memorains-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-deploy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/redTreeOnWall/memorains.git --path .agents/skills/memorains-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add redTreeOnWall/memorains --skill memorains-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install redTreeOnWall/memorains memorains-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/memorains-deploy .gemini/skills/memorains-deploy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memorains-deploy" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-deploy into .gemini/skills/memorains-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-deploy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install redTreeOnWall/memorains memorains-deployInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add redTreeOnWall/memorains --skill memorains-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/memorains-deploy .github/skills/memorains-deploy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memorains-deploy" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-deploy into .github/skills/memorains-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-deploy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add redTreeOnWall/memorains --skill memorains-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install redTreeOnWall/memorains memorains-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/memorains-deploy .opencode/skills/memorains-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memorains-deploy" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-deploy into .opencode/skills/memorains-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-deploy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memorains-deploy- GitHub stars
- 124
- Token cost
- ~974 tokens
- SKILL.md length
- 372 words
- Files
- 2
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Deploy memorains to production servers. An agent skill from redTreeOnWall/memorains.
- The user wants to deploy
- SKILL.md covers Step 0: Determine where to…, Prerequisites, Preferred: deploy with the… and Manual steps (fallback), plus 1 more section
- Runs Shell scripts from its folder; calls ssh, bash and scp
- Release memorains
What it does
Memorains Deploy is an agent skill from redTreeOnWall/memorains. Deploy memorains to production servers. Use when the user wants to deploy, ship, push, or release memorains, or mentions putting it on the server/VPS/production.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `deploy_web.sh`).
It sits in DevOps & Cloud, covering Deployment. The licence is MIT.
When your agent uses it
- The user wants to deploy
- Release memorains
- Mentions putting it on the server/VPS/production
Example prompts
- “/memorains-deploy”
Requirements
- Node.js
- A Bash shell
What it can do on your machine
Read from SKILL.md and the folder at commit a9de01b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Shell), which the agent can run.
Shell commands in SKILL.md call:
sshbashscp
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use ssh and scp, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memorains Deploy loads about 974 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 372 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: warnings
The automated check found patterns that need a careful read before installing.
- WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:15
a host from `~/.ssh/config`, shell history, README files, or past sessions.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from redTreeOnWall/memorains at commit a9de01b, republished under its MIT licence (© redTreeOnWall). 372 words, ~974 tokens.
Download SKILL.mdSave it as
.claude/skills/memorains-deploy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- memorains-deploy
- description
- Deploy memorains to production servers. Use when the user wants to deploy, ship, push, or release memorains, or mentions putting it on the server/VPS/production.
Memorains Deploy
Deploy the memorains project to one or more production servers.
Step 0: Determine where to deploy
If the user already specified which host(s) to deploy to, use them.
Otherwise, ask: "Which server(s) should I deploy to?" — and wait. Never infer
a host from ~/.ssh/config, shell history, README files, or past sessions.
Prerequisites
- SSH access to the target servers must work (key-based auth)
- Servers must have
podmanandpodman-composeinstalled
Preferred: deploy with the script
The companion script deploy_web.sh (in this skill directory) automates the
whole flow: it builds the package, discovers each host's project root from the
running reno_note_nodejs container mount, uploads, restarts the containers,
and verifies the result. Hosts are always passed as arguments — the script
contains no host information.
Run it from the repository root (walk up from .agents/skills/memorains-deploy/
to the repository root, i.e. <PROJECT_ROOT>):
bash <PROJECT_ROOT>/.agents/skills/memorains-deploy/deploy_web.sh -y <HOST> [HOST...]Useful flags:
| Flag | Effect |
|---|---|
-y, --yes | Skip the confirmation prompt |
--no-build | Reuse the existing script/out/package.tar.gz |
--no-verify | Skip the post-deploy container/HTTP checks |
Example:
bash <PROJECT_ROOT>/.agents/skills/memorains-deploy/deploy_web.sh -y example.com note.example.comIf the script exits non-zero — or a host's containers are already down so its
project root cannot be discovered (in that case export DEPLOY_PROJECT_ROOT or
fall back to the manual steps) — continue with the manual steps below.
Show full SKILL.md (174 more words)Show less
Manual steps (fallback)
Execute these steps in order for each server. Wait for each step to complete before starting the next.
For each host, discover the project root and package directory by inspecting the running containers. Run this on the server:
ssh <HOST> "podman inspect reno_note_nodejs --format '{{range .Mounts}}{{if eq .Destination \"/app/server\"}}{{.Source}}{{end}}{{end}}'"This returns the mount source path like <PROJECT_ROOT>/package/server. Strip
the trailing /server to get the package directory, and strip /package to get
the project root where package.tar.gz should be uploaded.
For example, /srv/app/note/package/server → package dir:
/srv/app/note/package, project root: /srv/app/note.
If no containers are running, ask the user for the project root path.
1. Build the web package locally
cd <PROJECT_ROOT>/script && bash build_web_package.shThis produces out/package.tar.gz.
2. Upload to the server
scp <PROJECT_ROOT>/script/out/package.tar.gz <HOST>:<PROJECT_ROOT>/3. Stop and remove existing containers
ssh <HOST> "cd <PACKAGE_DIR> && podman-compose down 2>&1 || true"The || true handles the case where no containers are currently running.
4. Clean and extract the new package
ssh <HOST> "rm -rf <PACKAGE_DIR> && cd <PROJECT_ROOT> && tar -zxf package.tar.gz"5. Start the new containers
ssh <HOST> "cd <PACKAGE_DIR> && podman-compose up -d"6. Verify deployment
ssh <HOST> "podman ps --filter name=reno_note --format '{{.Names}} {{.Status}}'"All three containers (reno_note_mariadb, reno_note_nodejs, reno_note_nginx)
should show as Up.
What gets deployed
| Container | Purpose |
|---|---|
reno_note_mariadb | MariaDB database (data persisted via named volume) |
reno_note_nodejs | Express + WebSocket server (Node.js Alpine) |
reno_note_nginx | Nginx reverse proxy (ports 80/443) |
© redTreeOnWall, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/memorains-deploy of redTreeOnWall/memorains.
- SKILL.md
- deploy_web.sh
Open the folder on GitHubat commit a9de01b
Compare with similar skills
Memorains Deploy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Memorains Deploy this skillredTreeOnWall/memorains | 124 | — | ~974 | Automated safety check: Warn | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 62k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
More from redTreeOnWall/memorains
Memorains DB Backup
redTreeOnWall/memorains
Back up the memorains production database and download the dump to the local backups/ directory.
Memorains GitHub Release
redTreeOnWall/memorains
Tag a new version, create a GitHub release with organized release notes, build all packages, and upload artifacts.
Related
Categories
Questions about Memorains Deploy
What does Memorains Deploy do?
Deploy memorains to production servers. An agent skill from redTreeOnWall/memorains. Memorains Deploy is an agent skill from redTreeOnWall/memorains. Deploy memorains to production servers.
When should I use Memorains Deploy?
Memorains Deploy fits situations like: the user wants to deploy; release memorains; mentions putting it on the server/VPS/production.
How do I install Memorains Deploy in Claude Code?
Run `npx skills add redTreeOnWall/memorains --skill memorains-deploy -a claude-code`. Or copy the skill folder (.agents/skills/memorains-deploy in redTreeOnWall/memorains) into .claude/skills/memorains-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Memorains Deploy in Codex?
Run `npx skills add redTreeOnWall/memorains --skill memorains-deploy -a codex`. Or copy the skill folder (.agents/skills/memorains-deploy in redTreeOnWall/memorains) into .agents/skills/memorains-deploy in your project. Codex loads it when a task matches its description.
Can I use Memorains Deploy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add redTreeOnWall/memorains --skill memorains-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memorains-deploy, .gemini/skills/memorains-deploy, .github/skills/memorains-deploy and .opencode/skills/memorains-deploy in your project.
What does Memorains Deploy need to run?
Going by SKILL.md and its folder, Memorains Deploy needs a shell for the scripts in its folder and the command-line tools its instructions call (ssh, bash and scp). Our summary lists: Node.js; A Bash shell.
Does Memorains Deploy access the network?
SKILL.md contains no URLs. Its commands use ssh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Memorains Deploy safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Memorains Deploy use?
Memorains Deploy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Memorains Deploy use?
About 974 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Memorains Deploy?
Skills that share tags, products or a category with Memorains Deploy: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memorains Deploy?
redTreeOnWall (a GitHub user) maintains it in redTreeOnWall/memorains, which has 124 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: redTreeOnWall/memorains on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.