pm-sim

Redirect users from pm-sim to the polymarket-paper-trader package.

372|52|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/agent-next/polymarket-paper-trader --skill pm-sim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-sim
Source: https://github.com/agent-next/polymarket-paper-trader/tree/main/skill/pm-sim
Command: npx skills add https://github.com/agent-next/polymarket-paper-trader --skill pm-sim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pm-sim has been renamed to polymarket-paper-trader. This skill provides a clear migration path and points users to the updated package to continue working with the project.

Core Features & Use Cases

  • Migration guidance from the older pm-sim to polymarket-paper-trader, ensuring a smooth transition for existing users.
  • Preservation of existing workflows: all pm-sim features are now available in the new package.
  • Suitable for development teams updating automation scripts, CI pipelines, and dependency references.

Quick Start

Install polymarket-paper-trader to continue using the updated package.

Frequently Asked Questions about pm-sim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from the deprecated pm-sim package?

To migrate from the deprecated pm-sim package, install the updated polymarket-paper-trader package and update your automation scripts and dependency references to point to the new name. All existing features are preserved in the new package.

Why is pm-sim deprecated and what replaced it?

The pm-sim package is deprecated because it was renamed to polymarket-paper-trader. You need to update your installation scripts and CI pipelines to reference polymarket-paper-trader to continue receiving updates and using the project.

What is the best way to update CI pipelines referencing pm-sim?

The best way to update CI pipelines referencing pm-sim is to replace the deprecated package name with polymarket-paper-trader in your installation scripts and dependency configurations. This ensures a smooth transition while preserving all existing workflows.

Can I keep my existing automation workflows after updating from pm-sim?

Yes, you can keep your existing automation workflows after updating from pm-sim. All features from the deprecated package are fully available in polymarket-paper-trader, ensuring your development workflows remain intact during the migration.

Does migrating to polymarket-paper-trader require any configuration changes?

Migrating to polymarket-paper-trader primarily requires updating package references in your installation scripts and CI pipelines. The skill provides clear migration instructions to ensure a smooth transition from the deprecated pm-sim name to the updated package.