Zapier Status
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
Diagnose a worker that is growing memory or being OOM-killed: separate a JS-heap leak from native growth, take a V8 heap snapshot of a live worker in place (never uploading it), and walk the…
Install Profile Worker Memory
$ npx skills add activepieces/activepieces --skill profile-worker-memory -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install activepieces/activepieces profile-worker-memory --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/activepieces/activepieces.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/profile-worker-memory .claude/skills/profile-worker-memory && 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 "profile-worker-memory" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/profile-worker-memory into .claude/skills/profile-worker-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "profile-worker-memory", 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/activepieces/activepieces/tree/main/.agents/skills/profile-worker-memoryType 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 activepieces/activepieces --skill profile-worker-memory -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install activepieces/activepieces profile-worker-memory --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/profile-worker-memory .agents/skills/profile-worker-memory && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "profile-worker-memory" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/profile-worker-memory into .agents/skills/profile-worker-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "profile-worker-memory", 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 activepieces/activepieces --skill profile-worker-memory -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install activepieces/activepieces profile-worker-memory --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/profile-worker-memory .cursor/skills/profile-worker-memory && 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 "profile-worker-memory" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/profile-worker-memory into .cursor/skills/profile-worker-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "profile-worker-memory", 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/activepieces/activepieces.git --path .agents/skills/profile-worker-memory--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 activepieces/activepieces --skill profile-worker-memory -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install activepieces/activepieces profile-worker-memory --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/profile-worker-memory .gemini/skills/profile-worker-memory && 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 "profile-worker-memory" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/profile-worker-memory into .gemini/skills/profile-worker-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "profile-worker-memory", 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 activepieces/activepieces profile-worker-memoryInstalls 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 activepieces/activepieces --skill profile-worker-memory -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/profile-worker-memory .github/skills/profile-worker-memory && 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 "profile-worker-memory" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/profile-worker-memory into .github/skills/profile-worker-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "profile-worker-memory", 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 activepieces/activepieces --skill profile-worker-memory -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install activepieces/activepieces profile-worker-memory --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/profile-worker-memory .opencode/skills/profile-worker-memory && 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 "profile-worker-memory" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/profile-worker-memory into .opencode/skills/profile-worker-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "profile-worker-memory", 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
profile-worker-memory- GitHub stars
- 25k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 789 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Diagnose a worker that is growing memory or being OOM-killed: separate a JS-heap leak from native growth, take a V8 heap snapshot of a live worker in place (never uploading it), and walk the…
- Works in 5 steps: Confirm it is actually OOM, and find… → JS heap or native? Decide before you… → Snapshot in place → …
- A self-hoster reports memory correlates with pod age
- SKILL.md covers 1. Confirm it is actually OOM,…, 2. JS heap or native? Decide…, 3. Snapshot in place and 4. Parse it off the worker…, plus 3 more sections
- Calls docker and node
What it does
Profile Worker Memory is an agent skill from activepieces/activepieces. Diagnose a worker that is growing memory or being OOM-killed: separate a JS-heap leak from native growth, take a V8 heap snapshot of a live worker in place (never uploading it), and walk the retainer path back to the code that holds the memory. Use when a self-hoster reports 'memory correlates with pod age', workers restart on their own, or a container sits near its limit.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering MCP servers and Workflow automation. It works with Model Context Protocol. The repository describes itself as: AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents.
When your agent uses it
- A self-hoster reports memory correlates with pod age
- Workers restart on their own
- A container sits near its limit
Example prompts
- “memory correlates with pod age”
- “/profile-worker-memory”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Confirm it is actually OOM, and find what is dying
- JS heap or native? Decide before you snapshot
- Snapshot in place
- Parse it off the worker process
- Walk the retainer path — this is the answer
What it can do on your machine
Read from SKILL.md and the folder at commit 566f00e. 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
Shell commands in SKILL.md call:
dockernode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, 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
Profile Worker Memory loads about 1.7k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 789 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 passed
The automated check found no risky patterns in SKILL.md.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 789 words (~1,731 tokens).
“Never ask anyone to upload a heap snapshot. It contains connection tokens, API keys, and customer step data verbatim — a customer will refuse, and they are right to. This procedure keeps the snapshot on their box and moves only…”
- name
- profile-worker-memory
Files
Just SKILL.md in .agents/skills/profile-worker-memory of activepieces/activepieces.
Open the folder on GitHubat commit 566f00e
Compare with similar skills
Profile Worker Memory 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 |
|---|---|---|---|---|---|---|
| Profile Worker Memory this skillactivepieces/activepieces | 25k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Zapier Statuszapier/zapier-mcp | 430 | — | ~1.8k | Automated safety check: Pass | MIT | |
| n8n Multi-Instance Targetingczlonkowski/n8n-skills | 6.4k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Agents Onboardingfazer-ai/agents | 118 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| N8n MCP Tools Expertdavila7/claude-code-templates | 32k | 8 repos | ~3.2k | Automated safety check: Pass | MIT | |
| n8n MCP Tools Expertczlonkowski/n8n-skills | 6.4k | — | ~7.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
n8n Multi-Instance Targeting
czlonkowski/n8n-skills
Keeps an n8n MCP session pointed at the right n8n instance, with rules for discovering, switching and verifying the target before credential writes and for recovering from misroutes.
Agents Onboarding
fazer-ai/agents
Conduz a jornada de onboarding 'do zero ao agente de atendimento' do fazer.ai agents num VPS, escolhendo o orquestrador de deploy (Tier A Coolify, B Portainer, C compose genérico para VM crua ou…
N8n MCP Tools Expert
davila7/claude-code-templates
Expert guide for using n8n-mcp MCP tools effectively. An agent skill from davila7/claude-code-templates.
n8n MCP Tools Expert
czlonkowski/n8n-skills
Guides the agent in choosing and calling n8n-mcp tools: finding nodes, validating configurations, deploying templates, managing workflows, folders and credentials, and auditing an instance.
- Official
MCP Urgent Caller Triage
zapier/gtm-cheat-codes
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers to legal client and matter context, and preparing a callback list for human review.
More from activepieces/activepieces
All 14 skills in this repoAnalyze Logs
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
Activepieces Design System
activepieces/activepieces
Design system for Activepieces (open-source AI automation platform, "open source replacement for Zapier").
Piece Builder
activepieces/activepieces
Build and edit Activepieces pieces (integrations) — creating new pieces, adding actions or triggers, or fixing bugs in existing ones.
Profile App Cpu
activepieces/activepieces
Find what is burning CPU in a live app container without restarting it: separate the JS thread from GC and libuv, open the V8 inspector in place with SIGUSR1, take a CPU profile over CDP, and…
Triage Dependabot Alerts
activepieces/activepieces
Triage Dependabot dependency vulnerability alerts for the Activepieces repo — pull open alerts, dedupe to distinct (package, advisory), confirm the vulnerable package + API is actually used, and…
Triage Image Cves
activepieces/activepieces
Scan an Activepieces Docker image with grype for OS/base-image (deb) and application (npm) CVEs of High/Critical severity.
Related
Works with
Categories
Questions about Profile Worker Memory
What does Profile Worker Memory do?
Diagnose a worker that is growing memory or being OOM-killed: separate a JS-heap leak from native growth, take a V8 heap snapshot of a live worker in place (never uploading it), and walk the…. Profile Worker Memory is an agent skill from activepieces/activepieces. Diagnose a worker that is growing memory or being OOM-killed: separate a JS-heap leak from native growth, take a V8 heap snapshot of a live worker in place (never uploading it), and walk the retainer path back to the code that holds the memory.
When should I use Profile Worker Memory?
Profile Worker Memory fits situations like: A self-hoster reports memory correlates with pod age; workers restart on their own; A container sits near its limit.
How do I install Profile Worker Memory in Claude Code?
Run `npx skills add activepieces/activepieces --skill profile-worker-memory -a claude-code`. Or copy the skill folder (.agents/skills/profile-worker-memory in activepieces/activepieces) into .claude/skills/profile-worker-memory in your project. Claude Code loads it when a task matches its description.
How do I install Profile Worker Memory in Codex?
Run `npx skills add activepieces/activepieces --skill profile-worker-memory -a codex`. Or copy the skill folder (.agents/skills/profile-worker-memory in activepieces/activepieces) into .agents/skills/profile-worker-memory in your project. Codex loads it when a task matches its description.
Can I use Profile Worker Memory 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 activepieces/activepieces --skill profile-worker-memory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/profile-worker-memory, .gemini/skills/profile-worker-memory, .github/skills/profile-worker-memory and .opencode/skills/profile-worker-memory in your project.
What does Profile Worker Memory need to run?
Going by SKILL.md and its folder, Profile Worker Memory needs the command-line tools its instructions call (docker and node). Our summary lists: Docker.
Does Profile Worker Memory access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Profile Worker Memory safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Profile Worker Memory use?
Profile Worker Memory has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Profile Worker Memory use?
About 1.7k tokens (SKILL.md is roughly 6.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 Profile Worker Memory?
Skills that share tags, products or a category with Profile Worker Memory: Zapier Status (zapier/zapier-mcp, 430 stars), n8n Multi-Instance Targeting (czlonkowski/n8n-skills, 6.4k stars), Agents Onboarding (fazer-ai/agents, 118 stars) and N8n MCP Tools Expert (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Profile Worker Memory?
activepieces (a GitHub organization) maintains it in activepieces/activepieces, which has 24,961 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.
Source: activepieces/activepieces on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.