Constraints that only bite in a real managed-package install of Portwood — global visibility, Flow Apex-Defined types, namespace-prefixed keys, USERMODE on internal reads, immutable API names.
$ npx skills add Portwood-Global-Solutions/Portwood --skill managed-package-rules -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Portwood-Global-Solutions/Portwood managed-package-rules --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/Portwood-Global-Solutions/Portwood.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/managed-package-rules .claude/skills/managed-package-rules && 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 "managed-package-rules" agent skill from https://github.com/Portwood-Global-Solutions/Portwood/tree/main/.claude/skills/managed-package-rules into .claude/skills/managed-package-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managed-package-rules", 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/Portwood-Global-Solutions/Portwood/tree/main/.claude/skills/managed-package-rulesType 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 Portwood-Global-Solutions/Portwood --skill managed-package-rules -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Portwood-Global-Solutions/Portwood managed-package-rules --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Portwood-Global-Solutions/Portwood.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/managed-package-rules .agents/skills/managed-package-rules && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "managed-package-rules" agent skill from https://github.com/Portwood-Global-Solutions/Portwood/tree/main/.claude/skills/managed-package-rules into .agents/skills/managed-package-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managed-package-rules", 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 Portwood-Global-Solutions/Portwood --skill managed-package-rules -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Portwood-Global-Solutions/Portwood managed-package-rules --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Portwood-Global-Solutions/Portwood.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/managed-package-rules .cursor/skills/managed-package-rules && 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 "managed-package-rules" agent skill from https://github.com/Portwood-Global-Solutions/Portwood/tree/main/.claude/skills/managed-package-rules into .cursor/skills/managed-package-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managed-package-rules", 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/Portwood-Global-Solutions/Portwood.git --path .claude/skills/managed-package-rules--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 Portwood-Global-Solutions/Portwood --skill managed-package-rules -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Portwood-Global-Solutions/Portwood managed-package-rules --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Portwood-Global-Solutions/Portwood.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/managed-package-rules .gemini/skills/managed-package-rules && 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 "managed-package-rules" agent skill from https://github.com/Portwood-Global-Solutions/Portwood/tree/main/.claude/skills/managed-package-rules into .gemini/skills/managed-package-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managed-package-rules", 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 Portwood-Global-Solutions/Portwood managed-package-rulesInstalls 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 Portwood-Global-Solutions/Portwood --skill managed-package-rules -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Portwood-Global-Solutions/Portwood.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/managed-package-rules .github/skills/managed-package-rules && 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 "managed-package-rules" agent skill from https://github.com/Portwood-Global-Solutions/Portwood/tree/main/.claude/skills/managed-package-rules into .github/skills/managed-package-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managed-package-rules", 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 Portwood-Global-Solutions/Portwood --skill managed-package-rules -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Portwood-Global-Solutions/Portwood managed-package-rules --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Portwood-Global-Solutions/Portwood.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/managed-package-rules .opencode/skills/managed-package-rules && 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 "managed-package-rules" agent skill from https://github.com/Portwood-Global-Solutions/Portwood/tree/main/.claude/skills/managed-package-rules into .opencode/skills/managed-package-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managed-package-rules", 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.
managed-package-rulesConstraints that only bite in a real managed-package install of Portwood — global visibility, Flow Apex-Defined types, namespace-prefixed keys, USERMODE on internal reads, immutable API names.
Managed Package Rules is an agent skill from Portwood-Global-Solutions/Portwood. Constraints that only bite in a real managed-package install of Portwood — global visibility, Flow Apex-Defined types, namespace-prefixed keys, USERMODE on internal reads, immutable API names. Use when adding Apex a subscriber must see, building a Flow action, or debugging something that works in a scratch org but fails in a package install.
Its SKILL.md is about 1.2k 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 Documents & Office, covering CRM management. It works with Salesforce. The repository describes itself as: Free, native document generation for Salesforce. PDF, DOCX, XLSX, PPTX — merge tags, images, barcodes, QR codes, bulk generation, Flow actions. 100% Apex + LWC, zero external… The licence is Apache-2.0.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 70ede0c. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Managed Package Rules loads about 1.2k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 597 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.
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.
The full file from Portwood-Global-Solutions/Portwood at commit 70ede0c, republished under its Apache-2.0 licence (© Portwood-Global-Solutions). 597 words, ~1,165 tokens.
.claude/skills/managed-package-rules/SKILL.md (or your agent's skills folder).Portwood ships as Managed 2GP, namespace portwoodglobal. A large class of bugs
exists only in a real subscriber install and cannot be reproduced in a no-namespace
scratch org. If something works in dev and fails in an install, start here.
global Apex is visible to subscriberspublic classes and methods are invisible in a subscriber org.
@InvocableMethod must be global to appear in a subscriber's Flow Builder.global, along with their inner
types, fields and methods.For a type to be selectable as a Flow Apex-Defined variable in a subscriber org:
global class.@AuraEnabled members.global no-arg constructor.Missing any one produces the same symptom: the action appears, but its variable type can't be selected. This cost three separate releases to get right, each time because only one of the four was missing. Verify in a real subscriber install or a namespaced scratch org — a no-namespace staging org cannot show you the failure.
Everything shipped is immutable: DocGen_Template__c, DocGenService, DocGen_Admin,
the portwoodglobal namespace, the Canvas picklist value. Display names (labels,
descriptions, user-visible strings) can change; API names cannot.
Two scheduled job names deliberately keep their old strings because they're matched by
CronJobDetail.Name in orgs that already scheduled them: DocGen Signature Reminders
and DocGen Chart CV Reaper.
2GP also cannot drop Apex classes without the "Remove Metadata Components" DevHub feature — the workaround is inert stubs.
In a subscriber org, SObject field keys come back namespace-prefixed:
row.Field__c is undefined in a shipped package — it's row.portwoodglobal__Field__c.
Use @salesforce/schema imports or a normalizing mapper in LWC.getPopulatedFieldsAsMap() keys are prefixed too. Prefer direct field access.Neither reproduces in a no-namespace org. A namespaced build is the real gate.
WITH USER_MODE on internal readsPortwood's internal ContentVersions (docgen_tmpl_html_*, docgen_tmpl_xml_*) have
ContentDocumentLink.Visibility = InternalUsers, which is invisible under
USER_MODE — the read silently returns empty and the caller falls back to something
degraded. Use the FLS-guard + WITH SYSTEM_MODE hybrid for these.
The same applies to a newly packaged field: the build's test user has no permission
set, so WITH USER_MODE fails the package build with "No such column" on a field that
plainly exists. Use SYSTEM_MODE plus an FLS guard for internal config reads.
@AuraEnabled(cacheable=true) serves stale empty results to guests. Never cache
context-sensitive Apex.SYSTEM_MODE query must be token-keyed, never keyed by a
guessable Id — that shape has already produced one IDOR.recordId. Check
sharing before debugging the component.Portwood is 100% native — no external services, APIs, or callouts, and document data never leaves the org. Client-side libraries are vendored as pinned static resources, not pulled from npm at build time. If you add or update one: keep it patched, retain its license/NOTICE, and disclose it.
Extension points exist precisely so the non-native hop can live outside the package —
see DocGenAiProvider and DocGenDataProvider, both resolved by Type.forName with a
namespace fallback.
A namespaced pre-flight org catches build traps in minutes rather than after a 20–40
minute package build: deploy plus RunLocalTests, without assigning the permission
set, so you see exactly what the build's test user sees.
© Portwood-Global-Solutions, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/managed-package-rules of Portwood-Global-Solutions/Portwood.
Open the folder on GitHubat commit 70ede0c
Managed Package Rules 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 |
|---|---|---|---|---|---|---|
| Managed Package Rules this skillPortwood-Global-Solutions/Portwood | 126 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Automation Sandbox Post Copy Config Generateforcedotcom/sf-skills | 1.1k | — | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Automation Sandbox Post Copy Config Generateforcedotcom/sf-skills | 1.1k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Gh Bot Commentjetstreamapp/jetstream | 127 | — | ~616 | Automated safety check: Pass | Custom licence | |
| External Consumersforcedotcom/salesforcedx-vscode | 1k | — | ~1.8k | Automated safety check: Pass | BSD-3-Clause | |
| Salesforce DeveloperJeffallan/claude-skills | 12k | — | ~1.9k | Automated safety check: Pass | MIT |
forcedotcom/sf-skills
Generate the JSON config file that the Salesforce sandbox post-copy automation tool consumes, from a customer SOP in any format (PDF, xlsx, csv, JSON, docx, Markdown, plain text, or a screenshot of…
forcedotcom/sf-skills
Generate the JSON config file that the Salesforce sandbox post-copy automation tool consumes, from a customer SOP in any format (PDF, xlsx, csv, JSON, docx, Markdown, plain text, or a screenshot of…
jetstreamapp/jetstream
Post GitHub PR/issue comments, reviews, and review replies as the Jetstream bot account instead of the user's personal account.
forcedotcom/salesforcedx-vscode
Known external consumers of APIs from this monorepo's extensions.
Jeffallan/claude-skills
Writes Apex, Lightning Web Components and SOQL for the Salesforce platform, with bulkified triggers, governor-limit checks, 90% test coverage and Salesforce DX deployment.
mukul975/Anthropic-Cybersecurity-Skills
Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…
Portwood-Global-Solutions/Portwood
Work on Portwood's Canvas designer (docGenCanvas LWC and canvasModel.js).
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
Portwood-Global-Solutions/Portwood
Author or repair a Portwood HTML template that renders correctly through Blob.toPdf (Flying Saucer).
Portwood-Global-Solutions/Portwood
Decide whether a Portwood bug report is a real code defect or a template-authoring problem, before any code is written.
Portwood-Global-Solutions/Portwood
Fix a Portwood merge-tag or parser bug correctly across all of its resolution paths.
Portwood-Global-Solutions/Portwood
Run Portwood's test suites — the one-command QA harness, the anonymous-Apex e2e scripts, Apex unit tests, prettier, and Code Analyzer.
Works with
Constraints that only bite in a real managed-package install of Portwood — global visibility, Flow Apex-Defined types, namespace-prefixed keys, USERMODE on internal reads, immutable API names. Managed Package Rules is an agent skill from Portwood-Global-Solutions/Portwood. Constraints that only bite in a real managed-package install of Portwood — global visibility, Flow Apex-Defined types, namespace-prefixed keys, USERMODE on internal reads, immutable API names.
Managed Package Rules fits situations like: adding Apex a subscriber must see; building a Flow action; debugging something that works in a scratch org but fails in a package install.
Run `npx skills add Portwood-Global-Solutions/Portwood --skill managed-package-rules -a claude-code`. Or copy the skill folder (.claude/skills/managed-package-rules in Portwood-Global-Solutions/Portwood) into .claude/skills/managed-package-rules in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Portwood-Global-Solutions/Portwood --skill managed-package-rules -a codex`. Or copy the skill folder (.claude/skills/managed-package-rules in Portwood-Global-Solutions/Portwood) into .agents/skills/managed-package-rules in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Portwood-Global-Solutions/Portwood --skill managed-package-rules -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managed-package-rules, .gemini/skills/managed-package-rules, .github/skills/managed-package-rules and .opencode/skills/managed-package-rules in your project.
SKILL.md names no scripts, command-line tools or credentials: Managed Package Rules is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Managed Package Rules is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Managed Package Rules: Automation Sandbox Post Copy Config Generate (forcedotcom/sf-skills, 1.1k stars), Automation Sandbox Post Copy Config Generate (forcedotcom/sf-skills, 1.1k stars), Gh Bot Comment (jetstreamapp/jetstream, 127 stars) and External Consumers (forcedotcom/salesforcedx-vscode, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Portwood-Global-Solutions (a GitHub organization) maintains it in Portwood-Global-Solutions/Portwood, which has 126 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.
Source: Portwood-Global-Solutions/Portwood on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
