npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

super-pencil

v1.0.1

Published

Master skill for using Pencil MCP - loads core workflow and dispatches to specialized skills

Downloads

188

Readme

Super Pencil

Master skill for using Pencil MCP - loads core workflow and dispatches to specialized skills for editing .pen files safely.

Installation

Option 1: Install via npm

npm install -g super-pencil

Option 2: Manual Installation

Copy the skill folder to your OpenCode skills directory:

Windows:

# Clone or download this repository
# Then copy to skills directory
Copy-Item -Path "<path-to-super-pencil>" -Destination "$env:USERPROFILE\.config\opencode\skills\super-pencil" -Recurse -Force

macOS/Linux:

# Clone or download this repository
# Then copy to skills directory
cp -r <path-to-super-pencil> ~/.config/opencode/skills/super-pencil

Option 3: Use install.sh script

./install.sh

Quick Start

Once installed, load the skill in your AI assistant:

Load skill: super-pencil

The skill will guide you through the 8-step workflow for safe .pen file editing.

Skill Structure

super-pencil/
├── SKILL.md                          # Main entry point
├── super-pencil-core/
│   └── SKILL.md                      # Core editing workflow
├── super-pencil-antipatterns/
│   └── SKILL.md                      # Common mistakes to avoid
├── super-pencil-path-debugging/
│   └── SKILL.md                      # Path rendering issues
└── super-pencil-troubleshooting/
    └── SKILL.md                      # Error diagnosis

When to Use Each Skill

| Skill | Use When | |-------|----------| | super-pencil | Starting any Pencil MCP task (load first) | | super-pencil-core | Need step-by-step editing workflow | | super-pencil-antipatterns | Before complex edits, review design decisions | | super-pencil-path-debugging | Path stroke renders in wrong position | | super-pencil-troubleshooting | MCP returns errors or edits do nothing |

Core Workflow

  1. Open fileopen_document
  2. Load schemaget_editor_state(include_schema=true)
  3. Read nodesbatch_get with patterns
  4. Set placeholderU("frameId",{placeholder:true})
  5. Edit batchesbatch_design (max 25 ops)
  6. Screenshotget_screenshot
  7. Debug if needed → Load related skill
  8. Remove placeholderU("frameId",{placeholder:false})

Non-Negotiable Rules

  1. Always load schema first
  2. Use placeholder flags during work
  3. Keep batches small (max 25 operations)
  4. Validate visually with screenshots
  5. Use fresh binding names every batch call

License

Apache-2.0

Author

Glacier Xiaowei

Related Projects