How do I install the HTML Ppt Zhangzara Pin And Paper skill?

Run npx skillmds@latest add gabrielmoreira/html-ppt-zhangzara-pin-and-paper in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is HTML Ppt Zhangzara Pin And Paper safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with HTML Ppt Zhangzara Pin And Paper?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is HTML Ppt Zhangzara Pin And Paper free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published HTML Ppt Zhangzara Pin And Paper?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

HTML Ppt Zhangzara Pin And Paper by gabrielmoreira

Name: HTML Ppt Zhangzara Pin And Paper
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

HTML Ppt Zhangzara Pin And Paper

A field-biology capstone on urban pollinator decline — the survey design, the data, the contribution, and the caveats. Built as a decision-grade coursework defense deck for faculty reviewers.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Pin & Paper

Yellow paper with safety-pin illustrations, ink-blue handwritten Caveat, paper-grain texture.

A single self-contained HTML deck — typography, palette, decorative system, and slide vocabulary are all tuned together. Mixing layouts across templates breaks the system; stay inside this one.

At a glance

Scheme: light
Formality: medium
Density: medium
Slides in demo: 11

Best for

Anything that should feel hand-crafted, warm, and literary: qualitative research findings, founder reflections, longform brand stories, workshop debriefs. The signature safety-pin illustrations and paper-grain texture make it especially good for any deck — including tech or business — that wants personality and warmth over polish.

Avoid for

Decks that need to feel digital-native polished or rigorously data-driven — handwritten Caveat is intentionally informal.

Workflow

Clone example.html AND the assets/ folder into the user's workspace. This template ships an assets/deck-stage.js runtime (keyboard navigation, stage rendering) and an assets/styles.css stylesheet. The HTML references them as assets/deck-stage.js and assets/styles.css, so both must sit next to the cloned HTML or those paths will 404 in the generated artifact and navigation/styling will silently break. Inlining the JS/CSS into a single <script>/<style> block in the HTML is an acceptable alternative when a single self-contained file is preferred.
Replace placeholder content with the user's real headlines, body copy, numbers, names, dates, and section labels. Match existing dimensions when swapping image placeholders.
Preserve the design system. Never substitute fonts, recolor the palette, restructure the layout grid, or strip decorative elements (corner brackets, paper grain, geometric shapes, illustrated SVGs). They are part of the identity.
Adjust deck length by duplicating layouts. If the user has more content than the demo holds, duplicate an existing slide of the most appropriate layout. If less, drop slides from the bottom. Update page-number labels.
Designing missing layouts: if a slide needs a layout the template doesn't have, design it from scratch using the same fonts, palette, decorative vocabulary, spacing rhythm, and component grammar — never bail to a different template.
Keep the navigation runtime as shipped. If the deck ships an assets/deck-stage.js or inline keyboard handler, leave it intact.

Output contract

Emit between <artifact> tags:

<artifact identifier="zhangzara-pin-and-paper" type="text/html" title="Deck Title">
<!doctype html>
<html>...</html>
</artifact>

Source & license

Vendored from upstream MIT-licensed zarazhangrui/beautiful-html-templates.

The full upstream MIT license text — including the original copyright notice — ships in this skill at LICENSE and must be redistributed alongside any copy of example.html, template.json, or any vendored assets/ runtime. See template.json for the upstream metadata snapshot.

---name: html-ppt-zhangzara-pin-and-paperdescription: A field-biology capstone on urban pollinator decline — the survey design, the data, the contribution, and the caveats. Built as a decision-grade coursework defense deck for faculty reviewers.--- # Pin & Paper > Yellow paper with safety-pin illustrations, ink-blue handwritten Caveat, paper-grain texture. A single self-contained HTML deck — typography, palette, decorative system, and slide vocabulary are all tuned together. Mixing layouts across templates breaks the system; stay inside this one. ## At a glance - **Scheme:** light - **Formality:** medium - **Density:** medium - **Slides in demo:** 11 ## Best for Anything that should feel hand-crafted, warm, and literary: qualitative research findings, founder reflections, longform brand stories, workshop debriefs. The signature safety-pin illustrations and paper-grain texture make it especially good for any deck — including tech or business — that wants personality and warmth over polish. ## Avoid for Decks that need to feel digital-native polished or rigorously data-driven — handwritten Caveat is intentionally informal. ## Workflow 1. **Clone `example.html` AND the `assets/` folder** into the user's workspace. This template ships an `assets/deck-stage.js` runtime (keyboard navigation, stage rendering) and an `assets/styles.css` stylesheet. The HTML references them as `assets/deck-stage.js` and `assets/styles.css`, so both must sit next to the cloned HTML or those paths will 404 in the generated artifact and navigation/styling will silently break. Inlining the JS/CSS into a single `<script>`/`<style>` block in the HTML is an acceptable alternative when a single self-contained file is preferred. 2. **Replace placeholder content** with the user's real headlines, body copy, numbers, names, dates, and section labels. Match existing dimensions when swapping image placeholders. 3. **Preserve the design system.** Never substitute fonts, recolor the palette, restructure the layout grid, or strip decorative elements (corner brackets, paper grain, geometric shapes, illustrated SVGs). They are part of the identity. 4. **Adjust deck length by duplicating layouts.** If the user has more content than the demo holds, duplicate an existing slide of the most appropriate layout. If less, drop slides from the bottom. Update page-number labels. 5. **Designing missing layouts:** if a slide needs a layout the template doesn't have, design it from scratch using the same fonts, palette, decorative vocabulary, spacing rhythm, and component grammar — never bail to a different template. 6. **Keep the navigation runtime as shipped.** If the deck ships an `assets/deck-stage.js` or inline keyboard handler, leave it intact. ## Output contract Emit between `<artifact>` tags: ``` <artifact identifier="zhangzara-pin-and-paper" type="text/html" title="Deck Title"> <!doctype html> <html>...</html> </artifact> ``` ## Source & license Vendored from upstream MIT-licensed [`zarazhangrui/beautiful-html-templates`](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/pin-and-paper). The full upstream MIT license text — including the original copyright notice — ships in this skill at [`LICENSE`](./LICENSE) and must be redistributed alongside any copy of `example.html`, `template.json`, or any vendored `assets/` runtime. See `template.json` for the upstream metadata snapshot.

Frequently asked questions