JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
Create or update user-focused Packmind documentation in apps/doc/ that explains features in clear task-oriented language without technical implementation details.
Install Creating End User Documentation For Packmind
$ npx skills add PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PackmindHub/packmind creating-end-user-documentation-for-packmind --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/PackmindHub/packmind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/creating-end-user-documentation-for-packmind .claude/skills/creating-end-user-documentation-for-packmind && 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 "creating-end-user-documentation-for-packmind" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/creating-end-user-documentation-for-packmind into .claude/skills/creating-end-user-documentation-for-packmind/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-end-user-documentation-for-packmind", 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/PackmindHub/packmind/tree/main/.claude/skills/creating-end-user-documentation-for-packmindType 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 PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PackmindHub/packmind creating-end-user-documentation-for-packmind --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/creating-end-user-documentation-for-packmind .agents/skills/creating-end-user-documentation-for-packmind && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "creating-end-user-documentation-for-packmind" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/creating-end-user-documentation-for-packmind into .agents/skills/creating-end-user-documentation-for-packmind/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-end-user-documentation-for-packmind", 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 PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PackmindHub/packmind creating-end-user-documentation-for-packmind --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/creating-end-user-documentation-for-packmind .cursor/skills/creating-end-user-documentation-for-packmind && 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 "creating-end-user-documentation-for-packmind" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/creating-end-user-documentation-for-packmind into .cursor/skills/creating-end-user-documentation-for-packmind/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-end-user-documentation-for-packmind", 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/PackmindHub/packmind.git --path .claude/skills/creating-end-user-documentation-for-packmind--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 PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PackmindHub/packmind creating-end-user-documentation-for-packmind --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/creating-end-user-documentation-for-packmind .gemini/skills/creating-end-user-documentation-for-packmind && 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 "creating-end-user-documentation-for-packmind" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/creating-end-user-documentation-for-packmind into .gemini/skills/creating-end-user-documentation-for-packmind/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-end-user-documentation-for-packmind", 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 PackmindHub/packmind creating-end-user-documentation-for-packmindInstalls 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 PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/creating-end-user-documentation-for-packmind .github/skills/creating-end-user-documentation-for-packmind && 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 "creating-end-user-documentation-for-packmind" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/creating-end-user-documentation-for-packmind into .github/skills/creating-end-user-documentation-for-packmind/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-end-user-documentation-for-packmind", 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 PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PackmindHub/packmind creating-end-user-documentation-for-packmind --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PackmindHub/packmind.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/creating-end-user-documentation-for-packmind .opencode/skills/creating-end-user-documentation-for-packmind && 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 "creating-end-user-documentation-for-packmind" agent skill from https://github.com/PackmindHub/packmind/tree/main/.claude/skills/creating-end-user-documentation-for-packmind into .opencode/skills/creating-end-user-documentation-for-packmind/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-end-user-documentation-for-packmind", 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
creating-end-user-documentation-for-packmind- GitHub stars
- 317
- Token cost
- ~1.3k tokens
- SKILL.md length
- 572 words
- Files
- 1
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create or update user-focused Packmind documentation in apps/doc/ that explains features in clear task-oriented language without technical implementation details.
- Works in 9 steps: Analyze the Codebase → Review Existing Documentation → Determine Documentation Structure → …
- The user asks to document a feature
- SKILL.md covers Scope, Context Validation Checkpoints and Recipe Steps
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Creating End User Documentation For Packmind is an agent skill from PackmindHub/packmind. Create or update user-focused Packmind documentation in apps/doc/ that explains features in clear task-oriented language without technical implementation details. Use this skill whenever the user asks to document a feature, write or update user guides, create end-user docs, explain how something works for users, or convert developer-focused docs to user-friendly guides — even if they don't say "documentation" explicitly. Trigger on any request to explain, guide, or describe Packmind features from a user…
Its SKILL.md is about 1.3k 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 Writing & Content, covering Technical writing. The repository describes itself as: Packmind seamlessly captures your engineering playbook and turns it into AI context, guardrails, and governance. The licence is Apache-2.0.
When your agent uses it
- The user asks to document a feature
- Update user guides
- Create end-user docs
- Explain how something works for users
Example prompts
- “t say”
- “/creating-end-user-documentation-for-packmind”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8a10541. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Creating End User Documentation For Packmind loads about 1.3k tokens when it runs. Until then it costs about 142 tokens; SKILL.md has 572 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
The full file from PackmindHub/packmind at commit 8a10541, republished under its Apache-2.0 licence (© PackmindHub). 572 words, ~1,345 tokens.
Download SKILL.mdSave it as
.claude/skills/creating-end-user-documentation-for-packmind/SKILL.md (or your agent's skills folder).- name
- creating-end-user-documentation-for-packmind
- description
- Create or update user-focused Packmind documentation in `apps/doc/` that explains features in clear task-oriented language without technical implementation details. Use this skill whenever the user asks to document a feature, write or update user guides, create end-user docs, explain how something works for users, or convert developer-focused docs to user-friendly guides — even if they don't say "documentation" explicitly. Trigger on any request to explain, guide, or describe Packmind features from a user perspective.
Create clear and concise end-user documentation for Packmind features to empower users in accomplishing their tasks effectively while avoiding unnecessary technical details.
Scope
All documentation modifications MUST only be made within the apps/doc/ folder, which contains the official Packmind end-user documentation. Do not modify any other documentation files outside this directory.
Context Validation Checkpoints
- Have you analyzed the codebase to understand the feature thoroughly (backend API, packages, frontend, MCP server)?
- Have you reviewed existing documentation in
apps/doc/to understand the structure? - Do you know whether you need to create a new file or update an existing one within
apps/doc/? - Have you identified what users need to accomplish versus what developers need to know?
Recipe Steps
Step 1: Analyze the Codebase
Before writing any documentation, thoroughly understand the feature by analyzing backend API controllers and endpoints, packages domain logic and use cases, frontend UI components and forms, and MCP server tools and their parameters. Focus on identifying user-facing functionality versus internal processes.
Step 2: Review Existing Documentation
Read all existing files in apps/doc/ to understand the current documentation structure, identify where your new content fits, check for overlapping or related information, and determine if you need to create a new file or update existing ones. The documentation is organized into subdirectories: administration/, concepts/, getting-started/, governance/, linter/, security/, and tools/.
Step 3: Determine Documentation Structure
Based on your analysis, decide whether to create a new .mdx file in the appropriate apps/doc/ subdirectory for a distinct new feature, update existing files if extending current functionality, or reorganize by extracting related content into dedicated files if needed. Always place new documentation in the most appropriate existing subdirectory.
Step 4: Write User-Focused Content
Focus on end users who are using Packmind, not developers building it. Explain what users can accomplish, not how the system works internally. Use language that matches user goals and workflows. Be clear and concise, getting straight to the point with simple direct language. Avoid technical jargon and implementation details. Structure content for action: start with what the feature does, provide step-by-step instructions, and include clear examples of expected outcomes.
Show full SKILL.md (224 more words)Show less
Step 5: Avoid Common Mistakes
Skip technical implementation details like API endpoints, database schemas, or code architecture. Don't explain internal workflows or development processes. Avoid debugging information or development setup. Skip unnecessary sections like generic 'Best Practices' or 'Tips and Tricks' that don't solve real user problems. Remove references to development tools (nx, build processes), internal configuration (Sentry, Infisical), and code examples users won't interact with.
Step 6: Use Documentation Template
Structure your documentation with: Feature Name as title, brief description of what it accomplishes, Overview of what users can do and why it's useful, Main Process sections with step-by-step actions, Troubleshooting for common user-facing issues with clear solutions, and Related Documentation links to other relevant guides.
# [Feature Name]
Brief description of what this feature accomplishes for users.
## Overview
What users can do with this feature and why it's useful.
## [Main Process 1]
### Step 1: [Action]
Clear instructions with specific UI elements to click/interact with.
### Step 2: [Action]
Continue with logical sequence of user actions.
## Troubleshooting
- **Problem**: Specific user-facing issue
- **Solutions**: Clear steps to resolve
## Related Documentation
Link to other relevant how-to guides.Step 7: Remove Development Content
When updating existing documentation, remove architecture diagrams and technical sequences, code examples users don't interact with, development environment setup, internal tool configuration, API implementation details, and debug and development modes.
Step 8: Create Cross-References
Ensure your documentation integrates well by linking to related guides where appropriate, updating existing files to reference your new content, creating a logical flow between related processes, and avoiding duplicating information across multiple files.
Step 9: Review and Validate
Before finalizing, read through from a user's perspective, ensure all steps are actionable and clear, verify all links and references work, and check that the content matches actual UI/functionality.
© PackmindHub, 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
Files
Just SKILL.md in .claude/skills/creating-end-user-documentation-for-packmind of PackmindHub/packmind.
Open the folder on GitHubat commit 8a10541
Compare with similar skills
Creating End User Documentation For Packmind 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 |
|---|---|---|---|---|---|---|
| Creating End User Documentation For Packmind this skillPackmindHub/packmind | 317 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| JS Concept Resource Curatorleonardomso/33-js-concepts | 67k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
JS Concept Resource Curator
leonardomso/33-js-concepts
Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Writing Docs
nukeop/nuclear
A skill your agent uses when writing or editing documentation in packages/docs.
More from PackmindHub/packmind
All 35 skills in this repoMichel CLI Demo Recorder
PackmindHub/packmind
Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR.
Michel UI Demo Recorder
PackmindHub/packmind
Record polished UI demo videos and screenshots of a running web app using Playwright MCP — for client deliverables, release notes, feature walkthroughs, or bug repros.
Packmind Create Skill
PackmindHub/packmind
Guide for creating effective skills. An agent skill from PackmindHub/packmind.
Doc Audit
PackmindHub/packmind
Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage.
Feature Sprint
PackmindHub/packmind
Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.
Michel Packmind Engineer Review
PackmindHub/packmind
Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping…
Related
Categories
Questions about Creating End User Documentation For Packmind
What does Creating End User Documentation For Packmind do?
Create or update user-focused Packmind documentation in apps/doc/ that explains features in clear task-oriented language without technical implementation details. Creating End User Documentation For Packmind is an agent skill from PackmindHub/packmind. Create or update user-focused Packmind documentation in apps/doc/ that explains features in clear task-oriented language without technical implementation details.
When should I use Creating End User Documentation For Packmind?
Creating End User Documentation For Packmind fits situations like: the user asks to document a feature; update user guides; create end-user docs; explain how something works for users.
How do I install Creating End User Documentation For Packmind in Claude Code?
Run `npx skills add PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a claude-code`. Or copy the skill folder (.claude/skills/creating-end-user-documentation-for-packmind in PackmindHub/packmind) into .claude/skills/creating-end-user-documentation-for-packmind in your project. Claude Code loads it when a task matches its description.
How do I install Creating End User Documentation For Packmind in Codex?
Run `npx skills add PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a codex`. Or copy the skill folder (.claude/skills/creating-end-user-documentation-for-packmind in PackmindHub/packmind) into .agents/skills/creating-end-user-documentation-for-packmind in your project. Codex loads it when a task matches its description.
Can I use Creating End User Documentation For Packmind 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 PackmindHub/packmind --skill creating-end-user-documentation-for-packmind -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-end-user-documentation-for-packmind, .gemini/skills/creating-end-user-documentation-for-packmind, .github/skills/creating-end-user-documentation-for-packmind and .opencode/skills/creating-end-user-documentation-for-packmind in your project.
What does Creating End User Documentation For Packmind need to run?
SKILL.md names no scripts, command-line tools or credentials: Creating End User Documentation For Packmind is instructions for the agent only.
Does Creating End User Documentation For Packmind access the network?
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.
Is Creating End User Documentation For Packmind 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 Creating End User Documentation For Packmind use?
Creating End User Documentation For Packmind 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.
How many tokens does Creating End User Documentation For Packmind use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 Creating End User Documentation For Packmind?
Skills that share tags, products or a category with Creating End User Documentation For Packmind: JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars), Beads Documentation Style Guide (gastownhall/beads, 28k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars) and JS Concept Resource Curator (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Creating End User Documentation For Packmind?
PackmindHub (a GitHub organization) maintains it in PackmindHub/packmind, which has 317 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.
Source: PackmindHub/packmind on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.