How do I install the Viral App skill?

Run npx skillmds@latest add dvcrn/viral-app 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 Viral App safe to use?

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

Which AI agents work with Viral App?

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 Viral App free to use?

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

Who published Viral App?

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

Viral App by dvcrn — Agent Skill

Name: Viral App
Rating: 4.5 (4 reviews)
Author: dvcrn

File contents

viral-app

Use this skill when you need to read or manage data through the viral.app API.

When to use

Query analytics (accounts, videos, KPIs, exports).
Manage tracked entities (accounts, videos, exclusions, refresh runs).
Manage projects and creator hub resources.
Pull live platform data (TikTok, Instagram, YouTube).

Quick start

Ensure viral-app CLI is installed and available in PATH.

viral-app --help

Set API key:

export VIRAL_API_KEY="..."

Get this key from viral.app dashboard at Settings -> API Keys.

Verify access:

viral-app accounts-list --per-page 1

The wrapper injects x-api-key automatically from VIRAL_API_KEY unless a header is already passed.

Inputs to collect first

Task type: read/report or mutate/manage resources.
Org-scoped IDs: orgacc_*, orgproj_*, creator/campaign/payout IDs when relevant.
Platform and entity identifiers (tiktok|instagram|youtube, platform account/video IDs).
Time bounds (--date-range[from], --date-range[to]) for analytics tasks.
Pagination/scope (--per-page, filters) to keep output focused.

Command cookbook

Discover available operations:

viral-app --help
viral-app <command> --help

Common reads:

viral-app accounts-list --per-page 10
viral-app videos-list --per-page 10
viral-app analytics-get-kpis
viral-app analytics-top-videos --per-page 10
viral-app integrations-apps-list

Common mutations:

viral-app projects-create --body '{"name":"My Project"}'
viral-app accounts-tracked-refresh --body '{"accounts":["orgacc_..."]}'
viral-app projects-add-to-account --body '{"projectId":"orgproj_...","accountId":"orgacc_..."}'

Safety rules

Confirm intent before POST, PUT, PATCH, or DELETE unless the user explicitly asked for that mutation.
Run <command> --help before mutations to verify required flags and body schema.
Prefer narrow queries first (--per-page, filters, date ranges) before broad exports.
Keep output machine-readable by default; only switch format when requested.

Troubleshooting

401 UNAUTHORIZED: missing/invalid API key; verify VIRAL_API_KEY or -H "x-api-key: ..." value.
401 can also happen with expired/revoked keys or wrong org context.
429 or retry hints: back off and retry later; inspect response headers such as Retry-After.
Empty data arrays: validate filters, project/account IDs, and date range constraints.
Never expose API keys in commits; rotate keys after sharing for tests.

Agent defaults

Output defaults to JSON (RSH_OUTPUT_FORMAT=json unless overridden).
Auto-pagination defaults to disabled (RSH_NO_PAGINATE=true) for predictable scripted behavior.
Summarize key metrics after reads and explicitly call out write-side effects after mutations.

---name: viral-appdescription: Use the viral.app API from an agent with a local CLI for account analytics, tracked videos/accounts, projects, creator hub, and live data operations.---# viral-appUse this skill when you need to read or manage data through the viral.app API.## When to use- Query analytics (accounts, videos, KPIs, exports).- Manage tracked entities (accounts, videos, exclusions, refresh runs).- Manage projects and creator hub resources.- Pull live platform data (TikTok, Instagram, YouTube).## Quick start1. Ensure `viral-app` CLI is installed and available in `PATH`.```bashviral-app --help```2. Set API key:```bashexport VIRAL_API_KEY="..."```Get this key from viral.app dashboard at `Settings -> API Keys`.3. Verify access:```bashviral-app accounts-list --per-page 1```The wrapper injects `x-api-key` automatically from `VIRAL_API_KEY` unless a header is already passed.## Inputs to collect first- Task type: read/report or mutate/manage resources.- Org-scoped IDs: `orgacc_*`, `orgproj_*`, creator/campaign/payout IDs when relevant.- Platform and entity identifiers (`tiktok|instagram|youtube`, platform account/video IDs).- Time bounds (`--date-range[from]`, `--date-range[to]`) for analytics tasks.- Pagination/scope (`--per-page`, filters) to keep output focused.## Command cookbookDiscover available operations:```bashviral-app --helpviral-app <command> --help```Common reads:```bashviral-app accounts-list --per-page 10viral-app videos-list --per-page 10viral-app analytics-get-kpisviral-app analytics-top-videos --per-page 10viral-app integrations-apps-list```Common mutations:```bashviral-app projects-create --body '{"name":"My Project"}'viral-app accounts-tracked-refresh --body '{"accounts":["orgacc_..."]}'viral-app projects-add-to-account --body '{"projectId":"orgproj_...","accountId":"orgacc_..."}'```## Safety rules- Confirm intent before `POST`, `PUT`, `PATCH`, or `DELETE` unless the user explicitly asked for that mutation.- Run `<command> --help` before mutations to verify required flags and body schema.- Prefer narrow queries first (`--per-page`, filters, date ranges) before broad exports.- Keep output machine-readable by default; only switch format when requested.## Troubleshooting- `401 UNAUTHORIZED`: missing/invalid API key; verify `VIRAL_API_KEY` or `-H "x-api-key: ..."` value.- `401` can also happen with expired/revoked keys or wrong org context.- `429` or retry hints: back off and retry later; inspect response headers such as `Retry-After`.- Empty `data` arrays: validate filters, project/account IDs, and date range constraints.- Never expose API keys in commits; rotate keys after sharing for tests.## Agent defaults- Output defaults to JSON (`RSH_OUTPUT_FORMAT=json` unless overridden).- Auto-pagination defaults to disabled (`RSH_NO_PAGINATE=true`) for predictable scripted behavior.- Summarize key metrics after reads and explicitly call out write-side effects after mutations.

Frequently asked questions

Viral App