DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Create and maintain one family medical brief from reports, notes, or partial information.
$ npx skills add petergyang/fuck-cancer --skill fuck-cancer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install petergyang/fuck-cancer fuck-cancer --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/petergyang/fuck-cancer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/fuck-cancer .claude/skills/fuck-cancer && 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 "fuck-cancer" agent skill from https://github.com/petergyang/fuck-cancer/tree/main/skills/fuck-cancer into .claude/skills/fuck-cancer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fuck-cancer", 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/petergyang/fuck-cancer/tree/main/skills/fuck-cancerType 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 petergyang/fuck-cancer --skill fuck-cancer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install petergyang/fuck-cancer fuck-cancer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petergyang/fuck-cancer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/fuck-cancer .agents/skills/fuck-cancer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fuck-cancer" agent skill from https://github.com/petergyang/fuck-cancer/tree/main/skills/fuck-cancer into .agents/skills/fuck-cancer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fuck-cancer", 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 petergyang/fuck-cancer --skill fuck-cancer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install petergyang/fuck-cancer fuck-cancer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petergyang/fuck-cancer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/fuck-cancer .cursor/skills/fuck-cancer && 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 "fuck-cancer" agent skill from https://github.com/petergyang/fuck-cancer/tree/main/skills/fuck-cancer into .cursor/skills/fuck-cancer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fuck-cancer", 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/petergyang/fuck-cancer.git --path skills/fuck-cancer--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 petergyang/fuck-cancer --skill fuck-cancer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install petergyang/fuck-cancer fuck-cancer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petergyang/fuck-cancer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/fuck-cancer .gemini/skills/fuck-cancer && 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 "fuck-cancer" agent skill from https://github.com/petergyang/fuck-cancer/tree/main/skills/fuck-cancer into .gemini/skills/fuck-cancer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fuck-cancer", 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 petergyang/fuck-cancer fuck-cancerInstalls 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 petergyang/fuck-cancer --skill fuck-cancer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/petergyang/fuck-cancer.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/fuck-cancer .github/skills/fuck-cancer && 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 "fuck-cancer" agent skill from https://github.com/petergyang/fuck-cancer/tree/main/skills/fuck-cancer into .github/skills/fuck-cancer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fuck-cancer", 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 petergyang/fuck-cancer --skill fuck-cancer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install petergyang/fuck-cancer fuck-cancer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petergyang/fuck-cancer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/fuck-cancer .opencode/skills/fuck-cancer && 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 "fuck-cancer" agent skill from https://github.com/petergyang/fuck-cancer/tree/main/skills/fuck-cancer into .opencode/skills/fuck-cancer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fuck-cancer", 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.
fuck-cancerCreate and maintain one family medical brief from reports, notes, or partial information.
Fuck Cancer is an agent skill from petergyang/fuck-cancer. Create and maintain one family medical brief from reports, notes, or partial information. Use when the user asks any cancer-related question or shares any cancer-related update, including symptoms during a workup, diagnosis, pathology, biomarkers, staging, treatment, recurrence, appointments, trials, second opinions, or caregiving decisions.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `agents/openai.yaml`, `eval.md` and `scripts/search_trials.py`).
It sits in Documents & Office, covering Clinical and healthcare research. It works with Google Docs. The repository describes itself as: Create and update a practical brief to help patients and caregivers advocate for themselves. The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3c5a990. 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.
Ships 1 file in scripts/ (Python), which the agent can run.
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.
Fuck Cancer loads about 2.7k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 1,616 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); the scripts in this folder are not scanned.
The full file from petergyang/fuck-cancer at commit 3c5a990, republished under its MIT licence (© petergyang). 1,616 words, ~2,726 tokens.
.claude/skills/fuck-cancer/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Help a patient or caregiver understand what is happening and take the next useful step. Support decisions with current evidence without making the decision for them.
Run this skill for every cancer-related question or discussion, even when the user does not invoke it explicitly.
Turn a sentence, brain dump, report, screenshot, or scattered update into one source-of-truth brief with patient information, next steps, key facts, and a care log. Read all supplied material before responding.
Use the destination the user names. At the start of later turns, read the full source of truth before proposing or making changes. Never create a second tracker.
If a Google Doc has separate Overview and Log tabs, treat both tabs as one brief and read both at the start of every cancer-related turn:
Overview.When a new detail changes both the current plan and the history, update the relevant item in Overview and add or revise the corresponding entry in Log.
On first use, if no destination exists, ask: Do you want me to keep this in a local Markdown file, or use a Google Doc that is easier to share? Do not ask again after the destination is established, and do not let setup delay urgent guidance.
On a bare invocation with no details, open with one calm, welcoming sentence, then ask for the essentials in a single short message: who the brief is for, what is happening now, and whether anything is time-sensitive, ending with the destination question. Never open with the destination question alone or with a form.
alex-brief.md, in the current workspace.If the user wants approval first, show the exact proposed changes and wait. After an authorized edit, read the saved destination back, link it, state what changed, and name the immediate next step.
Pending; use Unknown - ask the care team only for a gap that could change the next decision.Do not give the user a long intake form. Ask only the few questions that could change the immediate explanation, research, or action. Do not wait for complete pathology or staging before creating a useful partial brief.
Use sources in this order:
Do not cite search snippets, SEO health sites, unsourced summaries, social posts, AI-generated medical pages, or unofficial copies of copyrighted resources such as UpToDate or NCCN. Treat an authorized user-supplied copy as evidence and state its date.
Use an official cancer dictionary for definitions. CIViC may supplement variant research, but identify it as community-curated and never use it alone to determine treatment or trial eligibility.
Relate every option to the known cancer type, stage, biomarkers, prior treatment, health, country, and goals. Present a concise numbered list. Each item gets a bold stem and two or three sentences covering why it may matter, the main tradeoff, and what the care team must confirm. Do not declare one treatment the answer.
Use the official ClinicalTrials.gov API through the bundled helper:
python3 scripts/search_trials.py --condition "Cancer type" --terms "stage, biomarker, or treatment setting" --country "Country" [--state "State or province"] [--near LAT,LON --radius-miles 50]When a home city is known, use its coordinates with --near; exact city matching can miss nearby sites. Rerun with --full-criteria only when the preview is insufficient.
Check the study status, the specific site's status, and the eligibility criteria. Return three to five candidates at most. For each, include the linked NCT number, intervention, phase, nearest open site, why it may fit, and what the site must confirm. Compare the trial with available standard care and mention meaningful travel, visit, cost, or randomization burdens when known. Never claim eligibility.
Return no more than three best-fit options. Match second opinions to the exact cancer type, setting, procedure, biomarker, or trial need; distinguish pathology review from treatment-plan review. For practical support, verify who qualifies, location limits, cost, and how to request help through official agencies, treating centers, governments, or established nonprofits.
Title it <First name>’s Brief. Do not put cancer, a diagnosis, or alarming language in the title unless the user asks.
Use these sections in order. Include only useful content; do not fill the brief with empty fields.
Put essential care-coordination details first: patient facts, medical or insurance numbers, family doctor, current care team, and important contacts. Keep appointments, scans, and deadlines in What to do next; do not create another contacts section.
Use a numbered list with no more than three priority actions. Start each with a specific bold stem and name the report, test, appointment, clinician, or date: Review biopsy and scan results before 8/31, not Review results.
Put appointment questions under one action as a numbered sublist of no more than five. Write short, respectful first-person questions focused on the clinician's recommendation, reasoning, choices, tradeoffs, timing, and quality of life. Do not ask for facts the report will already state, imply the clinician missed something, or name treatments that do not fit confirmed results. Phrase a possible referral as Would it be useful to involve...
Include trials, second opinions, or practical support only when they create a useful current action. If trials may matter but key pathology, stage, biomarkers, or treatment history are missing, state exactly what is needed before rerunning /fuck-cancer.
Use a concise numbered list with bold stems. Combine each finding, its meaning, and meaningful uncertainty in one or two sentences. Fold pending information into the related finding or action instead of creating a useless standalone bullet. Keep definitions out of this section.
Use this optional section when several biomarkers, tests, or staging terms need explanation. Define each in one or two short sentences, then connect it to the patient's confirmed result and the treatment category it may affect. Use a brief parenthetical earlier only when the reader must understand the term immediately; do not define the same term twice.
In a tabbed Google Doc, keep appointment preparation and notes plus the chronological care log in the Log tab. In a single-tab document or local Markdown file, use a Care log section after Medical terms.
Use a numbered list for the chronological care log, newest first. Use M/D for current-year events and the year alone for older history when the exact date does not matter. Include only decision-relevant milestones and never invent a date. Keep exploratory conversations, personalized-vaccine ideas, and other experimental possibilities here unless they create a current action.
Put sources inline. Link every NCT number and place a short official source link after each treatment or evidence claim. Do not add a reference section, research date, or disclaimer to the brief.
Write like a calm person who has read everything. Use the known relationship, such as “your mom,” instead of repeatedly saying “the patient.” Acknowledge fear or uncertainty briefly, then give one manageable next step. Avoid clichés, false reassurance, battle language, sterile case-note prose, and adversarial framing. Explain terms without talking down to the reader.
Keep the chat response short: what changed, what matters now, and the brief link.
© petergyang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in skills/fuck-cancer of petergyang/fuck-cancer.
Open the folder on GitHubat commit 3c5a990
Fuck Cancer 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 |
|---|---|---|---|---|---|---|
| Fuck Cancer this skillpetergyang/fuck-cancer | 147 | — | ~2.7k | Automated safety check: Pass | MIT | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Managing Google Workspacetaylorwilsdon/google_workspace_mcp | 3.3k | — | ~2.9k | Automated safety check: Pass | MIT | |
| DOCX Editor CnGostyan/docx-skill-4-cn-paper | 442 | — | ~10k | Automated safety check: Pass | Proprietary | |
| Colleague DistillationZhixiangLuo/10xProductivity | 479 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Gdoc To Markdowniurykrieger/claude-bedrock | 105 | 1 repos | ~3.8k | Automated safety check: Notes | MIT |
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
taylorwilsdon/google_workspace_mcp
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search).
Gostyan/docx-skill-4-cn-paper
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
ZhixiangLuo/10xProductivity
Distill a colleague into a reusable AI skill (work + persona) using tool connections — Slack, Slack AI, Jira, GHE, Bitbucket, Confluence, SharePoint, Teams, Outlook, Notion, Linear, Google Docs, and…
iurykrieger/claude-bedrock
Internal fetcher module for Google Docs and Sheets. An agent skill from iurykrieger/claude-bedrock.
kklimuk/docx-cli
Read, edit, redline, comment on, and create Microsoft Word .docx files.
Works with
Categories
Create and maintain one family medical brief from reports, notes, or partial information. Fuck Cancer is an agent skill from petergyang/fuck-cancer. Create and maintain one family medical brief from reports, notes, or partial information.
Fuck Cancer fits situations like: the user asks any cancer-related question; shares any cancer-related update; including symptoms during a workup; second opinions.
Run `npx skills add petergyang/fuck-cancer --skill fuck-cancer -a claude-code`. Or copy the skill folder (skills/fuck-cancer in petergyang/fuck-cancer) into .claude/skills/fuck-cancer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add petergyang/fuck-cancer --skill fuck-cancer -a codex`. Or copy the skill folder (skills/fuck-cancer in petergyang/fuck-cancer) into .agents/skills/fuck-cancer 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 petergyang/fuck-cancer --skill fuck-cancer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fuck-cancer, .gemini/skills/fuck-cancer, .github/skills/fuck-cancer and .opencode/skills/fuck-cancer in your project.
Going by SKILL.md and its folder, Fuck Cancer needs Python for the scripts in its folder. Our summary lists: Python 3.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Fuck Cancer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k 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 Fuck Cancer: DOCX (rvdbreemen/OTGW-firmware, 207 stars), Managing Google Workspace (taylorwilsdon/google_workspace_mcp, 3.3k stars), DOCX Editor Cn (Gostyan/docx-skill-4-cn-paper, 442 stars) and Colleague Distillation (ZhixiangLuo/10xProductivity, 479 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
petergyang (a GitHub user) maintains it in petergyang/fuck-cancer, which has 147 GitHub stars. The repository was last updated on August 26, 2026.
Source: petergyang/fuck-cancer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.