Automatically fills content placeholders by analyzing surrounding text and referenced external files.
Install
mkdir -p .claude/skills/ph && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10960" && unzip -o skill.zip -d .claude/skills/ph && rm skill.zipInstalls to .claude/skills/ph
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Fill a placeholder — infer the best content from surrounding context.Key capabilities
- →Infers content for placeholder tags
- →Analyzes surrounding context for generation
- →Resolves external resource references
- →Supports scope modifiers for precise filling
How it works
It reads the surrounding text and any referenced resources to generate content that fits naturally into the specified placeholder position.
Inputs & outputs
When to use ph
- →Generating transition sentences
- →Filling documentation stubs
- →Updating code placeholders with context-aware content
About this skill
Placeholder
Generate content that fits naturally at the tag position.
Input
- File path: the file being processed.
- Surrounding text: the paragraph or block where the
<@ph>tag appears. - Prompt (optional): hint about what to fill (e.g., "a transition sentence"). Default: infer from context.
Workflow
- Read the surrounding text before and after the tag. Read the full file if you need broader context.
- Generate content that fits naturally at that position in tone, style, and meaning.
- Write the result back to the file: replace the
<@ph>tag with the generated text.
Scope Modifiers
The surrounding text may contain scope modifier tags. Since <@ph> replaces only the tag itself (not surrounding content), scope modifiers primarily provide context:
- Protect
<< >>: Protected text is context only — do not modify it. Remove the<<>>delimiters in the output. - Field
(( )): If the<@ph>tag appears inside a field, generate content within that field only. Remove the(())delimiters in the output.
Context References
The prompt may contain context references wrapped in double backticks ( ``). These point to external resources (file paths, section titles, etc.) that you should look up.
- Read the referenced resource and use it to inform the generated content. E.g.,
<@ph: a summary sentence based on ``results.md``>— readresults.mdto generate an appropriate placeholder. - Resolve references relative to the source file's directory unless an absolute path is given.
- Remove the
Rules
- Output should read as if it was always part of the text.
- Keep it concise and contextually appropriate.
- Respect scope modifiers if present.
- Resolve all context references (
- The
<@ph>tag and all modifier delimiters (<< >>,(( )),
When not to use it
- →When the placeholder lacks sufficient surrounding context
- →When the user wants to manually define the content
Limitations
- →Depends on context quality
- →Requires removal of tags and modifiers
How it compares
It uses context-aware inference to fill placeholders rather than simple template substitution.
Compared to similar skills
ph side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ph (this skill) | 0 | 4mo | No flags | Beginner |
| docs-write | 22 | 6mo | No flags | Beginner |
| content-research-writer | 15 | 10mo | No flags | Beginner |
| doc-coauthoring | 16 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
doc-coauthoring
anthropics
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
teams-channel-post-writer
daymade
Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.