Install
$ agentstack add skill-iankiku-agent-skill-factory-adapt-a-standard-textbook-page-to-every-reading-level ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Adapt a standard textbook page to every reading level — skill template
Turn this template into a working skill by resolving every TODO. The seed prompt below is the published Anthropic example this template was derived from; your skill should generalize it for repeated, hands-off use.
Outcome
Opus 4.7 reads a single source page in detail and returns a finished file for each audience that needs it.
TODO: Restate the outcome for YOUR context in one sentence: who runs this, on what input, producing what artifact, how often.
Seed prompt (verbatim from source, © Anthropic PBC)
From the textbook spread, build me: 1) One slide deck (8–10 slides) covering the core ideas, with the diagram redrawn simply on its own slide 2) Three versions of a one-page reading handout — Level A, B, C — same concepts, different vocabulary and sentence length 3) A short exit-ticket worksheet (3 questions) that checks the standard, same questions for everyone
Required context and inputs
- Textbook page (photo, scan, or PDF)
- Learning standards/objectives document
- Class roster with reading-level groupings (optional)
- Claude Project with standards/rules (optional)
- TODO: exact file paths / folders / message formats this skill should expect
- TODO: domain context the model cannot infer (naming conventions, thresholds, house style)
Tools, connectors, APIs, and authentication
- No connectors detected on the source page; base Claude capabilities only
- TODO: confirm which connectors are enabled in the runtime that will execute this skill
- Authentication: connectors authenticate via their own OAuth flows — this skill must
NEVER ask for, store, or echo credentials, tokens, or API keys. If auth is missing, stop and tell the user which connector to enable.
Permissions and sensitive actions
- Reads: TODO (folders, channels, records this skill may read)
- Writes: TODO (what it may create/modify, and where)
- Held back for the primary agent / human: sending external communications, financial
transactions, deleting or overwriting originals, submitting web forms
Workflow
- Describe the task (attach page, standards, rules for each version)
- Give Claude context (upload photo/scan, standards/objectives, version rules)
- Claude creates the materials (slide deck, handouts, exit ticket)
- Follow up with refinement prompts
TODO: adapt the steps above (from the source page) into imperative instructions for the executing agent, including what to do between steps.
Decision points
- TODO: list each point where the skill must choose between paths, with the rule to apply
- Default rule: prefer the reversible option; when two readings of the input are
plausible, surface both rather than picking silently.
Validation criteria
- Output matches the outcome statement above (spot-check against the seed prompt's asks)
- Every factual claim is traceable to a provided input, connector record, or cited source
- TODO: add one domain-specific check a reviewer in your org would apply
Failure modes and fallbacks
- Expected files missing from the connected folder → list what was found, ask before proceeding on partial inputs
- Ambiguous or missing input → ask one targeted question; if unattended, state the assumption inline and proceed
- Any step would take a sensitive/irreversible action → stop and hand back to the user (see Delegation)
Delegation
Apply the repo's delegation policy (docs/delegation-policy.md — bundle or restate it if you install this skill outside the repo). Defaults for this template:
- Run single-agent unless a step fans out over independent items (files, records,
vendors, channels). Only independent work parallelizes.
- Each delegated task must ship with: the minimal context slice it needs, an explicit
output contract, a validation check the primary agent runs on the result, and a fallback if it returns empty or fails.
- Final review, synthesis, and every sensitive action listed above stay with the
primary agent.
- TODO: name the concrete subtasks (if any) that qualify for delegation here.
Attribution
Derived from Adapt a standard textbook page to every reading level (retrieved 2026-07-26). Seed prompt and workflow content © Anthropic PBC. Scaffold structure original to this repository.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: iankiku
- Source: iankiku/agent-skill-factory
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.