clipboard-posting
Use when the user asks to copy drafted content to the clipboard, copy it again, prepare something for LinkedIn, paste rich text into a social composer, or stage plain text for X. This skill tells Pi when to use the rich clipboard extension and which format/target to choose.
What this skill does
# Clipboard Posting
Use the `copy_rich_clipboard` tool for clipboard requests instead of explaining the workflow manually.
## When to use
Trigger this skill when the user says things like:
- "copy this to my clipboard"
- "put this on my clipboard"
- "copy it again"
- "make this paste nicely into LinkedIn"
- "prep this for X"
- "open LinkedIn and stage the formatted version"
## Workflow
1. Identify the content to copy.
- If the user already approved a draft in the conversation, use that exact draft.
- If the user says "copy it again", reuse the most recent approved version.
- Do not silently rewrite the content unless the user asks for edits.
2. Choose the correct format.
- `markdown` - default for rich-text paste targets like LinkedIn or other editors that preserve formatting.
- `html` - use when the user already supplied HTML and wants that copied as-is.
- `text` - use for plain-text destinations like X, terminals, or anywhere formatting should be stripped.
3. Choose the destination behavior.
- `target: linkedin-article` for the LinkedIn article composer.
- `target: linkedin-post` for a normal LinkedIn post flow.
- `target: x` for X compose.
- `target: none` when the user only wants the clipboard updated.
- If the user gives a specific URL to open, pass it via `openUrl`.
4. Call the tool directly.
### Tool examples
```json
{
"content": "# Draft post\n\nThis is ready to publish.",
"format": "markdown",
"target": "linkedin-article"
}
```
```json
{
"content": "Short plain-text post for X",
"format": "text",
"target": "x"
}
```
## Notes
- Prefer the tool over narrating manual clipboard steps.
- Preserve links, bullets, and paragraph breaks for LinkedIn-style content.
- Keep hashtags and URLs exactly as approved unless the user asks for changes.
- If the user wants to do it manually inside Pi, mention the commands `/copy-rich`, `/copy-linkedin`, and `/copy-x`.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.