paperclip-plugin-playbook-runner-otomatik 0.3.2 → 0.3.4

package/dist/manifest.js

@@ -6,7 +6,7 @@ var PLUGIN_ID = "paperclipai.playbook-runner";
 var manifest = {
   id: PLUGIN_ID,
   apiVersion: 1,
-  version: "0.3.2",
+  version: "0.3.4",
   displayName: "Agents & Workflows",
   description: "Runs agent-static flows: creates the child tasks of each phase, chains review tasks, counts review rounds, and escalates a loop that does not converge to the sector head.",
   author: "Local development plugin",

package/dist/manifest.js.map

@@ -1,7 +1,7 @@
 {
   "version": 3,
   "sources": ["../src/generated/skill.json", "../src/manifest.ts"],
-  "sourcesContent": ["{\"skills\":[{\"slug\":\"executive-task-orchestration\",\"title\":\"Executive task orchestration\",\"description\":\"Use when converting owner-approved company priorities into a Paperclip plan, choosing task owners, delegating work, or reviewing cross-team outcomes. Do not use to approve the CEO agent's own consequential actions.\",\"markdown\":\"---\\nname: executive-task-orchestration\\ndescription: >\\n  Use when converting owner-approved company priorities into a Paperclip plan, choosing task owners, delegating work, or reviewing cross-team outcomes. Do not use to approve the CEO agent's own consequential actions.\\n---\\n\\n# Executive task orchestration\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read company goals, existing Paperclip tasks, evidence, and current capacity.\\n2. Separate conversation from tracked work; create no task unless requested or authorized.\\n3. Define outcome, one owner, acceptance evidence, assumptions, dependencies, and human approval needs.\\n4. Delegate bounded work through linked tasks and review evidence before summarizing the outcome.\\n\\n## Expected result\\n\\nA concise priority decision, owner-assigned task plan, approval request, or evidence-backed closeout.\\n\\n## Stop and escalate\\n\\nEscalate budget, publication, hiring, production access, legal or safety exposure, and irreversible decisions to the human Owner.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/org/org-structure/\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n\"},{\"slug\":\"marketing-campaign-planning\",\"title\":\"Marketing campaign planning\",\"description\":\"Use when defining a campaign objective, audience, offer, positioning, message, channel mix, measurement, or campaign review. Do not use this skill to publish, spend, or promise results.\",\"markdown\":\"---\\nname: marketing-campaign-planning\\ndescription: >\\n  Use when defining a campaign objective, audience, offer, positioning, message, channel mix, measurement, or campaign review. Do not use this skill to publish, spend, or promise results.\\n---\\n\\n# Marketing campaign planning\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read COMPANY.md and BUSINESS.md and identify approved goals, audiences, proof, constraints, and voice.\\n2. Use current research to define one audience problem, offer, message, and measurable conversion.\\n3. Choose channels, owners, budget request, dates, dependencies, and stop criteria.\\n4. Review evidence against targets and recommend continue, revise, or stop.\\n\\n## Expected result\\n\\nA campaign brief with objective, audience, offer, evidence, message, channels, owners, measures, budget request, risks, approvals, and review date.\\n\\n## Stop and escalate\\n\\nDo not invent testimonials, results, audience evidence, or legal claims; seek human approval for budget and publication.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"technical-architecture-and-delegation\",\"title\":\"Technical architecture and delegation\",\"description\":\"Use when a development request needs technical discovery, stack selection, architecture decisions, a fullstack-versus-split decision, or developer assignments. Do not use to make unapproved production changes.\",\"markdown\":\"---\\nname: technical-architecture-and-delegation\\ndescription: >\\n  Use when a development request needs technical discovery, stack selection, architecture decisions, a fullstack-versus-split decision, or developer assignments. Do not use to make unapproved production changes.\\n---\\n\\n# Technical architecture and delegation\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect repository instructions, stack and versions, interfaces, data, deployment path, and constraints.\\n2. Define the smallest architecture that meets the approved outcome.\\n3. Choose one implementation owner or split work only when interfaces are stable and risk justifies it.\\n4. Write acceptance checks, security and privacy requirements, dependencies, test evidence, and release conditions.\\n\\n## Expected result\\n\\nA short technical decision record and implementation plan with named owners, interfaces, risks, and verification evidence.\\n\\n## Stop and escalate\\n\\nEscalate unknown production access, regulated data, security findings, major migrations, and infrastructure spend to the human Owner.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/org/org-structure/\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n\"},{\"slug\":\"n8n-workflow-design-and-operations\",\"title\":\"n8n workflow design and operations\",\"description\":\"Use when assessing, designing, implementing, testing, or handing off an approved n8n automation or MCP-exposed workflow.\",\"markdown\":\"---\\nname: n8n-workflow-design-and-operations\\ndescription: >\\n  Use when assessing, designing, implementing, testing, or handing off an approved n8n automation or MCP-exposed workflow.\\n---\\n\\n# n8n workflow design and operations\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm the CEO-selected approach, workflow owner, company instance, permitted data, and task acceptance criteria.\\n2. Map triggers, inputs, data movement, side effects, credentials, retries, idempotency, and failure handling before building.\\n3. Build the smallest maintainable workflow in a development or test environment; keep complex reusable business logic in versioned code where that improves testability.\\n4. Test expected, malformed, duplicate, timeout, rate-limit, and partial-failure cases and preserve redacted execution evidence.\\n5. Document monitoring, alerting, recovery, rollback, credential ownership, and human approval required before production activation.\\n\\n## Expected result\\n\\nA workflow design or handoff with owner, version, environment, data flow, integrations, test evidence, residual risks, monitoring, recovery, and approval state.\\n\\n## Stop and escalate\\n\\nStop before production activation, external messaging, destructive changes, or access to another company's data unless the assigned task and authorized human approval explicitly permit the action. Never expose secrets or unnecessary personal data.\\n\\n## References\\n\\n- https://docs.n8n.io/connect/connect-to-n8n-mcp-server/\\n- https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/\\n- https://docs.n8n.io/hosting/security/\\n\"},{\"slug\":\"operating-cadence-and-handoffs\",\"title\":\"Operating cadence and handoffs\",\"description\":\"Use when preparing a daily or weekly operating brief, coordinating cross-team dependencies, or diagnosing recurring workflow friction. Do not use to change company strategy or make external commitments.\",\"markdown\":\"---\\nname: operating-cadence-and-handoffs\\ndescription: >\\n  Use when preparing a daily or weekly operating brief, coordinating cross-team dependencies, or diagnosing recurring workflow friction. Do not use to change company strategy or make external commitments.\\n---\\n\\n# Operating cadence and handoffs\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read only approved priorities, task statuses, deadlines, and permitted service summaries.\\n2. Separate evidence, estimates, blockers, and owner decisions.\\n3. Rank the three most material actions and name one accountable owner for each.\\n4. Record dependencies, escalation routes, and a review date for any proposed process pilot.\\n\\n## Expected result\\n\\nAn owner-ready operating brief or handoff with status, priorities, accountable owners, evidence, and decisions required.\\n\\n## Stop and escalate\\n\\nDo not message customers, move money, reassign work against the reporting tree, or expose unnecessary personal data.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/org/org-structure/\\n- https://docs.paperclip.ing/guides/projects-workflow/routines/\\n\"},{\"slug\":\"qa-and-release\",\"title\":\"Risk-based QA and release\",\"description\":\"Use when planning tests, validating acceptance criteria, checking regressions, or preparing release evidence for a software change. Do not treat passing tests as proof of zero risk.\",\"markdown\":\"---\\nname: qa-and-release\\ndescription: >\\n  Use when planning tests, validating acceptance criteria, checking regressions, or preparing release evidence for a software change. Do not treat passing tests as proof of zero risk.\\n---\\n\\n# Risk-based QA and release\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Map each acceptance criterion to a reproducible check.\\n2. Prioritize user journeys, data boundaries, failure states, integrations, and supported versions by risk.\\n3. Run authorized local or staging checks and preserve commands, results, and defects.\\n4. Review unresolved findings, migration safety, monitoring, backup, rollback, and required approvals.\\n\\n## Expected result\\n\\nA risk-based test plan, reproducible findings, coverage limits, and release recommendation.\\n\\n## Stop and escalate\\n\\nBlock release recommendation for unresolved critical findings, missing authorization, or absent recovery evidence.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/agent-developer/writing-a-skill/\\n- https://github.com/microsoft/playwright-mcp\\n\"},{\"slug\":\"customer-care-triage\",\"title\":\"Customer care triage\",\"description\":\"Use when classifying customer messages, answering approved routine questions, preparing a support reply, or escalating a complaint or sensitive case. Do not provide unapproved legal, medical, safety, or financial advice.\",\"markdown\":\"---\\nname: customer-care-triage\\ndescription: >\\n  Use when classifying customer messages, answering approved routine questions, preparing a support reply, or escalating a complaint or sensitive case. Do not provide unapproved legal, medical, safety, or financial advice.\\n---\\n\\n# Customer care triage\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Check the company support policy, approved answer source, queue permissions, and response authority.\\n2. Classify intent, urgency, sensitivity, and responsible service owner.\\n3. Use only current approved facts; draft when send authority is absent.\\n4. Route uncertain or sensitive requests to a named human or qualified professional and record a minimized handoff.\\n\\n## Expected result\\n\\nA categorized queue item, approved answer or draft, or clear escalation with next action and owner.\\n\\n## Stop and escalate\\n\\nNever promise a legal, medical, refund, compliance, or commercial outcome. Minimize personal data and escalate potential harm or formal complaints.\\n\\n## References\\n\\n- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679\\n\"},{\"slug\":\"market-and-competitor-research\",\"title\":\"Market and competitor research\",\"description\":\"Use when investigating an audience, market opportunity, competitor offer, pricing, demand signal, or channel pattern. Do not present estimates as verified facts or infer private data.\",\"markdown\":\"---\\nname: market-and-competitor-research\\ndescription: >\\n  Use when investigating an audience, market opportunity, competitor offer, pricing, demand signal, or channel pattern. Do not present estimates as verified facts or infer private data.\\n---\\n\\n# Market and competitor research\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Define the decision the research must support and the permitted sources.\\n2. Collect dated evidence about customer needs, competitor offers, pricing, positioning, and channel presence.\\n3. Separate observations, estimates, and hypotheses; record source, method, freshness, and confidence.\\n4. Synthesize opportunity, counter-evidence, unknowns, and what should be tested next.\\n\\n## Expected result\\n\\nA concise source-linked research brief with evidence, limitations, opportunity hypotheses, and next validation step.\\n\\n## Stop and escalate\\n\\nDo not use restricted sources, infer sensitive traits, or claim market size or demand without a traceable method.\\n\\n## References\\n\\n- https://support.google.com/trends/answer/4365533\\n- https://github.com/HubSpot/agent-cli-skills\\n\"},{\"slug\":\"brand-positioning-and-creative-brief\",\"title\":\"Brand positioning and creative brief\",\"description\":\"Use when turning approved customer evidence into positioning, a campaign angle, creative direction, or a brief for visual assets. Do not invent company proof or change approved brand commitments.\",\"markdown\":\"---\\nname: brand-positioning-and-creative-brief\\ndescription: >\\n  Use when turning approved customer evidence into positioning, a campaign angle, creative direction, or a brief for visual assets. Do not invent company proof or change approved brand commitments.\\n---\\n\\n# Brand positioning and creative brief\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read approved company voice, offers, proof, and audience context.\\n2. Translate research into a customer problem, differentiated value, reason to believe, and message hierarchy.\\n3. Define creative concept, format, audience, placement, accessibility, and claim limits.\\n4. Present alternatives and evidence for owner review before production or publication.\\n\\n## Expected result\\n\\nA positioning statement and creative brief with audience, insight, promise, support, concept, format, and review needs.\\n\\n## Stop and escalate\\n\\nFlag unsupported claims, sensitive imagery, unclear rights, and any material change to brand promises.\\n\\n## References\\n\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"content-strategy-planning\",\"title\":\"Content strategy planning\",\"description\":\"Use when planning an editorial series, content calendar, audience education sequence, or reusable campaign content. Do not create volume without an audience need and measurable purpose.\",\"markdown\":\"---\\nname: content-strategy-planning\\ndescription: >\\n  Use when planning an editorial series, content calendar, audience education sequence, or reusable campaign content. Do not create volume without an audience need and measurable purpose.\\n---\\n\\n# Content strategy planning\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Start from approved audience questions, campaign objective, and source material.\\n2. Choose content themes, formats, channel roles, sequence, and an intended audience action.\\n3. Assign source checks, specialist review, voice review, owner, and publication date.\\n4. Define success measures and reuse rules before the content is produced.\\n\\n## Expected result\\n\\nAn editorial brief or calendar with themes, audience intent, formats, owners, sources, reviewers, and measures.\\n\\n## Stop and escalate\\n\\nPause on unsupported factual claims, regulated topics without qualified review, or reuse of identifiable customer stories without consent.\\n\\n## References\\n\\n- https://developers.google.com/search/docs/fundamentals/creating-helpful-content\\n\"},{\"slug\":\"evidence-based-copywriting\",\"title\":\"Evidence-based copywriting\",\"description\":\"Use when drafting or revising customer-facing marketing copy, a landing page, offer, advertisement, or email. Do not fabricate proof, urgency, scarcity, or guaranteed outcomes.\",\"markdown\":\"---\\nname: evidence-based-copywriting\\ndescription: >\\n  Use when drafting or revising customer-facing marketing copy, a landing page, offer, advertisement, or email. Do not fabricate proof, urgency, scarcity, or guaranteed outcomes.\\n---\\n\\n# Evidence-based copywriting\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read the approved voice, offer, audience, and evidence in company context.\\n2. Identify the audience problem, single promise, reason to believe, and next action.\\n3. Draft plainly with claims tied to named evidence and limits.\\n4. Check clarity, accessibility, channel fit, required review, and approval before publication.\\n\\n## Expected result\\n\\nA copy draft with audience, purpose, source notes for factual claims, CTA, and open approvals.\\n\\n## Stop and escalate\\n\\nEscalate health, safety, legal, financial, comparative, quantified, or testimonial claims for documented review.\\n\\n## References\\n\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"seo-audit-and-search-content\",\"title\":\"SEO audit and search content\",\"description\":\"Use when diagnosing organic-search visibility, prioritizing an SEO issue, or preparing a search-focused content brief. Do not promise rankings or use manipulative tactics.\",\"markdown\":\"---\\nname: seo-audit-and-search-content\\ndescription: >\\n  Use when diagnosing organic-search visibility, prioritizing an SEO issue, or preparing a search-focused content brief. Do not promise rankings or use manipulative tactics.\\n---\\n\\n# SEO audit and search content\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Check the site's technical and content context and identify the target user intent.\\n2. Use permitted Search Console or analytics evidence; distinguish query data from guesses.\\n3. Prioritize crawl, index, performance, accessibility, and content-quality issues by impact and confidence.\\n4. Write a change brief with current state, recommended action, validation evidence, and review date.\\n\\n## Expected result\\n\\nA prioritized SEO issue list or content brief with evidence and validation steps.\\n\\n## Stop and escalate\\n\\nDo not create doorway pages, mass-generated thin content, fake backlinks, or unsupported structured data.\\n\\n## References\\n\\n- https://developers.google.com/search/docs/fundamentals/creating-helpful-content\\n- https://developers.google.com/search/docs/crawling-indexing\\n\"},{\"slug\":\"paid-media-testing\",\"title\":\"Paid media testing\",\"description\":\"Use when designing, reviewing, or analyzing a paid advertising test. Do not launch ads, change bids, or spend budget without explicit authorization.\",\"markdown\":\"---\\nname: paid-media-testing\\ndescription: >\\n  Use when designing, reviewing, or analyzing a paid advertising test. Do not launch ads, change bids, or spend budget without explicit authorization.\\n---\\n\\n# Paid media testing\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm approved offer, audience, destination, budget envelope, and claim evidence.\\n2. Define campaign structure, conversion event, exclusions, creative variants, and tracking checks.\\n3. Set baseline, success threshold, stop rule, review window, and accountable human approver.\\n4. Analyze results with spend, qualified outcomes, attribution limits, and risks stated separately.\\n\\n## Expected result\\n\\nAn approval-ready test plan or evidence-based performance report.\\n\\n## Stop and escalate\\n\\nStop on tracking failure, unapproved claims, spend-limit uncertainty, audience-policy risk, or unapproved account changes.\\n\\n## References\\n\\n- https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server/\\n- https://github.com/google/agent-skills\\n\"},{\"slug\":\"social-channel-operations\",\"title\":\"Organic social channel operations\",\"description\":\"Use when adapting approved campaign material to social channels, planning a publishing schedule, or preparing moderation guidance. Do not publish or engage in disputes without authorization.\",\"markdown\":\"---\\nname: social-channel-operations\\ndescription: >\\n  Use when adapting approved campaign material to social channels, planning a publishing schedule, or preparing moderation guidance. Do not publish or engage in disputes without authorization.\\n---\\n\\n# Organic social channel operations\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm channel, audience, campaign objective, source facts, and approved voice.\\n2. Adapt one idea to the platform's format without changing its evidence or promise.\\n3. Prepare accessible assets, caption, CTA, alt text, timing, and moderation route.\\n4. Submit drafts for approval and record performance or recurring audience questions.\\n\\n## Expected result\\n\\nA channel-ready draft pack and schedule with sources, owner, moderation plan, and approval status.\\n\\n## Stop and escalate\\n\\nEscalate complaints, legal threats, sensitive disclosures, harassment, misinformation risk, or unclear response authority.\\n\\n## References\\n\\n- https://github.com/anthropics/skills/tree/main/skills/internal-comms\\n\"},{\"slug\":\"lifecycle-email-campaigns\",\"title\":\"Lifecycle email campaigns\",\"description\":\"Use when drafting a consent-based onboarding, lifecycle, retention, or customer update email sequence. Do not send to a list without approved audience basis and suppression checks.\",\"markdown\":\"---\\nname: lifecycle-email-campaigns\\ndescription: >\\n  Use when drafting a consent-based onboarding, lifecycle, retention, or customer update email sequence. Do not send to a list without approved audience basis and suppression checks.\\n---\\n\\n# Lifecycle email campaigns\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm audience source, communication purpose, legal basis or consent policy, and suppression rules.\\n2. Map the sequence to a customer lifecycle need and one clear action per message.\\n3. Draft subject, body, sender, preference and unsubscribe handling, and tracking.\\n4. Review claims, deliverability, segmentation, and approval before sending; measure meaningful outcomes.\\n\\n## Expected result\\n\\nAn email sequence brief or draft set with audience rules, timing, suppression, approval, and measures.\\n\\n## Stop and escalate\\n\\nStop if contact permission, opt-out handling, sender identity, or sensitive segmentation is unclear.\\n\\n## References\\n\\n- https://developers.google.com/workspace/guides/configure-mcp-servers\\n\"},{\"slug\":\"marketing-measurement\",\"title\":\"Marketing measurement and analysis\",\"description\":\"Use when defining campaign events, checking tracking, analyzing funnel performance, or preparing a marketing report. Do not change campaigns, budgets, or landing pages based on analysis alone.\",\"markdown\":\"---\\nname: marketing-measurement\\ndescription: >\\n  Use when defining campaign events, checking tracking, analyzing funnel performance, or preparing a marketing report. Do not change campaigns, budgets, or landing pages based on analysis alone.\\n---\\n\\n# Marketing measurement and analysis\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm objective, metric definitions, reporting period, data source, and known attribution limits.\\n2. Check event coverage and data quality before comparing results.\\n3. Analyze funnel stages with denominators, segments, and uncertainty visible.\\n4. Explain supported findings and recommend a test or decision for the accountable owner.\\n\\n## Expected result\\n\\nA measurement plan, source-linked analysis, or decision brief with definitions, limitations, and next action.\\n\\n## Stop and escalate\\n\\nDo not infer personal behavior beyond authorized aggregation or make causal claims from descriptive data alone.\\n\\n## References\\n\\n- https://developers.google.com/analytics/devguides/MCP\\n- https://posthog.com/docs/model-context-protocol\\n\"},{\"slug\":\"leadgen-strategy-and-funnel\",\"title\":\"Lead generation strategy and funnel\",\"description\":\"Use when defining an ideal customer segment, acquisition funnel, qualification criteria, channel test, or handoff to Sales. Do not maximize raw lead volume without fit and contact safeguards.\",\"markdown\":\"---\\nname: leadgen-strategy-and-funnel\\ndescription: >\\n  Use when defining an ideal customer segment, acquisition funnel, qualification criteria, channel test, or handoff to Sales. Do not maximize raw lead volume without fit and contact safeguards.\\n---\\n\\n# Lead generation strategy and funnel\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read approved offer, market evidence, privacy boundaries, and Sales acceptance criteria.\\n2. Define target segment, observable intent signals, exclusions, and conversion event.\\n3. Select a bounded channel experiment with source, cost/effort limit, and stop rule.\\n4. Agree qualification fields and handoff timing with the Sales owner; measure quality through the funnel.\\n\\n## Expected result\\n\\nA segment and funnel brief with qualification, contact rules, channel test, owner, measures, and handoff.\\n\\n## Stop and escalate\\n\\nEscalate unclear contact basis, sensitive profiling, purchased lists, or unsupported targeting data.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server\\n\"},{\"slug\":\"prospect-research-and-data-quality\",\"title\":\"Prospect research and data quality\",\"description\":\"Use when researching or cleaning a business prospect list for an approved purpose. Do not infer sensitive personal traits or treat public data as permission to contact.\",\"markdown\":\"---\\nname: prospect-research-and-data-quality\\ndescription: >\\n  Use when researching or cleaning a business prospect list for an approved purpose. Do not infer sensitive personal traits or treat public data as permission to contact.\\n---\\n\\n# Prospect research and data quality\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm research purpose, allowed sources, minimum fields, and contact policy.\\n2. Capture source, retrieval date, freshness, and confidence for important fields.\\n3. Check relevance, duplicates, exclusions, and conflicting information.\\n4. Return only necessary fields and document records removed or needing human review.\\n\\n## Expected result\\n\\nA source-linked prospect or segment evidence table with quality flags and permitted handoff fields.\\n\\n## Stop and escalate\\n\\nDo not scrape restricted sites, fabricate contact details, or export data without approved use and access.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679\\n\"},{\"slug\":\"outreach-campaign-operations\",\"title\":\"Outreach campaign operations\",\"description\":\"Use when preparing an approved outbound outreach sequence, audience rules, or campaign results report. Do not send messages or bypass suppression and opt-out controls.\",\"markdown\":\"---\\nname: outreach-campaign-operations\\ndescription: >\\n  Use when preparing an approved outbound outreach sequence, audience rules, or campaign results report. Do not send messages or bypass suppression and opt-out controls.\\n---\\n\\n# Outreach campaign operations\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Verify approved offer, list source, contact basis, segment, and exclusions.\\n2. Draft concise, relevant messages with honest personalization and a clear next step.\\n3. Check suppression, opt-out, frequency, sender, and CRM handoff rules.\\n4. Submit for approval; after authorized launch, report replies, qualified outcomes, complaints, and opt-outs.\\n\\n## Expected result\\n\\nAn outreach draft pack and launch checklist, or a campaign results and stop recommendation.\\n\\n## Stop and escalate\\n\\nPause on unclear permission, complaints, misleading claims, sensitive data, or missing unsubscribe handling.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server\\n\"},{\"slug\":\"administrative-operations-coordination\",\"title\":\"Administrative operations coordination\",\"description\":\"Use when converting internal decisions into action logs, coordinating administrative requests, or preparing routine operating records. Do not commit funds, sign agreements, or send external messages without approval.\",\"markdown\":\"---\\nname: administrative-operations-coordination\\ndescription: >\\n  Use when converting internal decisions into action logs, coordinating administrative requests, or preparing routine operating records. Do not commit funds, sign agreements, or send external messages without approval.\\n---\\n\\n# Administrative operations coordination\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm requester, purpose, due date, source record, and approving owner.\\n2. Separate decisions from discussion and assign one owner per action.\\n3. Prepare a reversible draft, calendar entry, or checklist using approved systems.\\n4. Record approval, completion evidence, and unresolved items in the source of truth.\\n\\n## Expected result\\n\\nA clear action record, request route, deadline list, or approval-ready administrative draft.\\n\\n## Stop and escalate\\n\\nEscalate legal, financial, access, privacy, and regulated-record decisions to their named owner.\\n\\n## References\\n\\n- https://developers.google.com/workspace/guides/configure-mcp-servers\\n\"},{\"slug\":\"finance-administration-review\",\"title\":\"Finance administration review\",\"description\":\"Use when reconciling source records, preparing invoice status, checking finance totals, or drafting an approval-ready payment pack. Do not execute payments or provide tax or accounting advice.\",\"markdown\":\"---\\nname: finance-administration-review\\ndescription: >\\n  Use when reconciling source records, preparing invoice status, checking finance totals, or drafting an approval-ready payment pack. Do not execute payments or provide tax or accounting advice.\\n---\\n\\n# Finance administration review\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm reporting period, currency, accounting owner, and authoritative source records.\\n2. Reconcile totals and preserve references to source documents.\\n3. Separate actuals, estimates, forecasts, and assumptions; explain variances.\\n4. Prepare proposed actions for review and record the human decision.\\n\\n## Expected result\\n\\nA traceable reconciliation, invoice list, variance note, or approval-ready finance pack.\\n\\n## Stop and escalate\\n\\nEscalate missing evidence, unusual payment changes, tax judgments, bank-detail changes, and payment execution.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n\"},{\"slug\":\"records-and-document-control\",\"title\":\"Records and document control\",\"description\":\"Use when maintaining a document register, checking versions and approvals, or preparing a controlled record for sharing. Do not delete records or invent retention periods.\",\"markdown\":\"---\\nname: records-and-document-control\\ndescription: >\\n  Use when maintaining a document register, checking versions and approvals, or preparing a controlled record for sharing. Do not delete records or invent retention periods.\\n---\\n\\n# Records and document control\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm record owner, authoritative location, purpose, sensitivity, and access scope.\\n2. Check version, approval status, date, and duplicate or stale copies.\\n3. Apply the approved naming and filing convention while preserving the source.\\n4. Record missing records, access questions, or retention decisions for the authorized owner.\\n\\n## Expected result\\n\\nAn evidence index, document inventory, version history, or minimized sharing proposal.\\n\\n## Stop and escalate\\n\\nEscalate legal holds, health or case records, deletion, external sharing, and retention changes.\\n\\n## References\\n\\n- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679\\n\"},{\"slug\":\"sales-pipeline-management\",\"title\":\"Sales pipeline management\",\"description\":\"Use when defining sales stages, reviewing pipeline quality, preparing a forecast, or improving the lead handoff from Marketing. Do not invent forecast certainty or change approved prices.\",\"markdown\":\"---\\nname: sales-pipeline-management\\ndescription: >\\n  Use when defining sales stages, reviewing pipeline quality, preparing a forecast, or improving the lead handoff from Marketing. Do not invent forecast certainty or change approved prices.\\n---\\n\\n# Sales pipeline management\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm approved offers, stage definitions, decision roles, and the reporting period.\\n2. Check stage evidence, next action, owner, value, and close conditions.\\n3. Identify stalled, unsupported, duplicate, or no-fit opportunities.\\n4. Summarize supported pipeline ranges, assumptions, handoffs, and owner decisions.\\n\\n## Expected result\\n\\nA stage definition, pipeline review, forecast range, and next-step owner list.\\n\\n## Stop and escalate\\n\\nEscalate pricing, contractual terms, claims, customer data access, and unsupported forecast assumptions.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n\"},{\"slug\":\"sales-lead-qualification\",\"title\":\"Sales lead qualification\",\"description\":\"Use when responding to a new enquiry, preparing discovery questions, or deciding whether a prospect meets approved fit and intent criteria. Do not pressure or mislead a buyer.\",\"markdown\":\"---\\nname: sales-lead-qualification\\ndescription: >\\n  Use when responding to a new enquiry, preparing discovery questions, or deciding whether a prospect meets approved fit and intent criteria. Do not pressure or mislead a buyer.\\n---\\n\\n# Sales lead qualification\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Check approved offer, qualification rules, response-time expectations, and contact history.\\n2. Ask only relevant questions about need, context, timing, decision process, and fit.\\n3. Record facts and direct quotes separately from hypotheses.\\n4. Route qualified prospects to the right seller and provide a clear next step or respectful no-fit response.\\n\\n## Expected result\\n\\nA concise qualification record, discovery brief, follow-up draft, or reasoned no-fit outcome.\\n\\n## Stop and escalate\\n\\nEscalate sensitive, regulated, legal, clinical, financial, or complaint-related enquiries.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n\"},{\"slug\":\"consultative-sales-proposals\",\"title\":\"Consultative sales proposals\",\"description\":\"Use when preparing a discovery summary, proposal, objection response, or customer follow-up for an approved offer. Do not promise outcomes outside the approved scope.\",\"markdown\":\"---\\nname: consultative-sales-proposals\\ndescription: >\\n  Use when preparing a discovery summary, proposal, objection response, or customer follow-up for an approved offer. Do not promise outcomes outside the approved scope.\\n---\\n\\n# Consultative sales proposals\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Summarize the buyer's stated problem, decision criteria, and desired outcome.\\n2. Match needs to an approved offer and identify gaps or exclusions.\\n3. Draft scope, deliverables, price source, assumptions, timing, and responsibilities.\\n4. Request human approval before sending and record the customer's decision and next step.\\n\\n## Expected result\\n\\nAn evidence-based discovery note, proposal draft, or buyer decision plan.\\n\\n## Stop and escalate\\n\\nDo not invent discounts, deadlines, guarantees, legal conclusions, or product capabilities.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"engineering-delivery-baseline\",\"title\":\"Engineering delivery baseline\",\"description\":\"Use for software implementation tasks across Next.js, MEAN, and WordPress repositories. Do not use to bypass repository instructions, tests, security review, or task approval.\",\"markdown\":\"---\\nname: engineering-delivery-baseline\\ndescription: >\\n  Use for software implementation tasks across Next.js, MEAN, and WordPress repositories. Do not use to bypass repository instructions, tests, security review, or task approval.\\n---\\n\\n# Engineering delivery baseline\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect the repository's instructions, existing patterns, versions, and relevant tests before changing files.\\n2. Restate the acceptance criteria and make the smallest scoped change.\\n3. Use authorized checks that match the task risk and project conventions; record commands and results.\\n4. Review the final diff for scope, security, regressions, documentation, and a clear handoff.\\n\\n## Expected result\\n\\nA scoped implementation with acceptance evidence, known limitations, and reviewer-ready change summary.\\n\\n## Stop and escalate\\n\\nDo not expose secrets, write production data, change unrelated architecture, or claim a check passed when it was not run.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/agent-developer/writing-a-skill/\\n- https://github.com/github/github-mcp-server\\n\"},{\"slug\":\"nextjs-development\",\"title\":\"Next.js development\",\"description\":\"Use when implementing or reviewing a Next.js feature, route, server action, API boundary, rendering behavior, or performance issue. Do not assume a router, runtime, cache, or Next.js version.\",\"markdown\":\"---\\nname: nextjs-development\\ndescription: >\\n  Use when implementing or reviewing a Next.js feature, route, server action, API boundary, rendering behavior, or performance issue. Do not assume a router, runtime, cache, or Next.js version.\\n---\\n\\n# Next.js development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read package manifests and repository guidance to identify Next.js version, App/Pages Router, runtime, and test setup.\\n2. Keep server-only secrets and privileged logic out of client bundles.\\n3. Follow the existing data-fetching, caching, authentication, and route patterns.\\n4. Use Next.js DevTools only when the documented version and local development-server prerequisites are met; verify behavior with project checks.\\n\\n## Expected result\\n\\nA version-aligned implementation or review with server/client boundaries and test evidence.\\n\\n## Stop and escalate\\n\\nEscalate new database, authentication, runtime, or deployment choices that exceed task scope.\\n\\n## References\\n\\n- https://nextjs.org/docs/app/guides/ai-agents\\n- https://nextjs.org/docs/app/guides/mcp\\n- https://github.com/vercel/next.js/tree/canary/skills\\n\"},{\"slug\":\"mean-stack-development\",\"title\":\"MEAN stack development\",\"description\":\"Use when implementing a feature across Angular, Node/Express, and MongoDB, or when working on one of those layers in a MEAN application. Do not assume library versions or production database access.\",\"markdown\":\"---\\nname: mean-stack-development\\ndescription: >\\n  Use when implementing a feature across Angular, Node/Express, and MongoDB, or when working on one of those layers in a MEAN application. Do not assume library versions or production database access.\\n---\\n\\n# MEAN stack development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect Angular, Node, Express, MongoDB, and data-access versions and existing boundaries.\\n2. Define typed API and validation contracts before changing dependent layers.\\n3. Use development data and review schema, index, migration, authorization, and query behavior.\\n4. Run appropriate unit, API, build, and browser checks and document results.\\n\\n## Expected result\\n\\nA coherent layer-specific or vertical-slice change with API, persistence, and UI evidence.\\n\\n## Stop and escalate\\n\\nDo not run destructive operations or production CRUD through MongoDB MCP; escalate schema changes and sensitive data access.\\n\\n## References\\n\\n- https://angular.dev/ai/agent-skills\\n- https://angular.dev/ai/mcp\\n- https://www.mongodb.com/docs/mcp-server/overview/\\n- https://expressjs.com/advanced/best-practice-security/\\n\"},{\"slug\":\"wordpress-site-maintenance\",\"title\":\"WordPress site maintenance\",\"description\":\"Use when diagnosing or maintaining a WordPress site, configuration, integration, upgrade, or migration. Do not edit WordPress core or run unapproved production changes.\",\"markdown\":\"---\\nname: wordpress-site-maintenance\\ndescription: >\\n  Use when diagnosing or maintaining a WordPress site, configuration, integration, upgrade, or migration. Do not edit WordPress core or run unapproved production changes.\\n---\\n\\n# WordPress site maintenance\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Identify WordPress, PHP, hosting, theme, plugin, and deployment versions and the site's existing architecture.\\n2. Reproduce the issue in local or staging and identify the responsible layer.\\n3. Prefer supported APIs, WP-CLI, reversible configuration, and documented migration steps.\\n4. Check backup, compatibility, permissions, performance, accessibility, and rollback evidence.\\n\\n## Expected result\\n\\nA bounded site fix or an upgrade/integration plan with reproducible checks and rollback notes.\\n\\n## Stop and escalate\\n\\nRequire human approval, backup, and rollback for production writes, migrations, credentials, or plugin changes.\\n\\n## References\\n\\n- https://developer.wordpress.org/\\n- https://developer.wordpress.org/cli/commands/\\n\"},{\"slug\":\"wordpress-plugin-development\",\"title\":\"WordPress plugin development\",\"description\":\"Use when designing, implementing, testing, or reviewing a WordPress plugin or custom functional extension. Do not edit WordPress core or third-party plugin source.\",\"markdown\":\"---\\nname: wordpress-plugin-development\\ndescription: >\\n  Use when designing, implementing, testing, or reviewing a WordPress plugin or custom functional extension. Do not edit WordPress core or third-party plugin source.\\n---\\n\\n# WordPress plugin development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect supported WordPress/PHP versions, plugin structure, hooks, APIs, and existing tests.\\n2. Check capabilities and authorization, nonces, validation, sanitization, escaping, and data lifecycle.\\n3. Implement the smallest change using supported extension points.\\n4. Run authorized checks and prepare compatibility, upgrade, security, and release evidence.\\n\\n## Expected result\\n\\nA maintainable plugin change with permission, data, compatibility, test, and release notes.\\n\\n## Stop and escalate\\n\\nEscalate external service calls, sensitive data, destructive migrations, and live-site writes.\\n\\n## References\\n\\n- https://developer.wordpress.org/plugins/\\n- https://developer.wordpress.org/plugins/security/\\n- https://github.com/WordPress/agent-skills\\n\"},{\"slug\":\"wordpress-theme-development\",\"title\":\"WordPress theme development\",\"description\":\"Use when implementing or reviewing a WordPress theme, block theme, template, pattern, theme.json setting, or editor/front-end presentation. Do not put persistent business logic in a theme.\",\"markdown\":\"---\\nname: wordpress-theme-development\\ndescription: >\\n  Use when implementing or reviewing a WordPress theme, block theme, template, pattern, theme.json setting, or editor/front-end presentation. Do not put persistent business logic in a theme.\\n---\\n\\n# WordPress theme development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Identify classic or block theme architecture, supported versions, theme.json, and design tokens.\\n2. Make presentation changes in the correct template, pattern, or style layer.\\n3. Check responsive behavior, editor/front-end parity, accessibility, and performance.\\n4. Capture visual and automated evidence for relevant templates and states.\\n\\n## Expected result\\n\\nA focused theme change with responsive, accessible, editor, and visual evidence.\\n\\n## Stop and escalate\\n\\nRoute persistent data, business logic, and functional integrations to a plugin or application layer.\\n\\n## References\\n\\n- https://developer.wordpress.org/themes/\\n- https://developer.wordpress.org/themes/global-settings-and-styles/\\n- https://github.com/WordPress/agent-skills\\n\"},{\"slug\":\"run-playbook\",\"title\":\"Run a playbook\",\"description\":\"Use when a Paperclip task carries a playbook, when you are asked to start one, or when your assigned task is a step of a playbook run (a child task created from a flow). Do not use for ordinary tasks that no playbook covers.\",\"markdown\":\"---\\nname: run-playbook\\ndescription: >\\n  Use when a Paperclip task carries a playbook, when you are asked to start one, or when your assigned task is a step of a playbook run (a child task created from a flow). Do not use for ordinary tasks that no playbook covers.\\n---\\n\\n# Run a playbook\\n\\nThis is an original, markdown-only Paperclip skill. It guides work; it does not grant access, make approvals, or replace Paperclip's own task status. Paperclip has no native playbook object: this skill builds the flow out of native tasks, blockers, task documents and execution policies.\\n\\n## Two kinds of playbook\\n\\n- **Checklist** \u2014 `PLAYBOOKS/NN-*.md` in your role folder. Ordered steps for one agent inside one task.\\n- **Flow** \u2014 `PLAYBOOKS/flows/*.yaml` in the folder of the role that owns it. Steps belong to different roles; each `task` step becomes its own Paperclip task, chained with blockers.\\n\\nIf no playbook fits, use the default delivery checklist below.\\n\\n## Run a checklist (one agent, one task)\\n\\n1. Keep the run register in the task document with key `playbook` (format: `templates/PLAYBOOK-REGISTER.md`, shown in the task as plain Markdown). If the document already exists, read it and resume; never start a second run.\\n2. Fill the header: task, one owner, approved outcome and acceptance checks, assumptions, escalation owner, Owner approval status. Copy the steps in order; step 1 is IN_PROGRESS, the rest PENDING.\\n3. Work one step at a time. A step becomes PASS only with evidence on its line (link, artifact, task comment, check output). Then activate only the next step.\\n4. When blocked, mark the step BLOCKED with the reason and who must act, leave later steps PENDING, and put the Paperclip task itself in a waiting state: `blocked` with `blockedByIssueIds`, or a pending interaction with `in_review` for a human decision. Text in the register alone does not stop or wake anyone. Then stop.\\n5. Update the document with the revision-safe procedure of the Paperclip skill (`PUT /api/issues/{issueId}/documents/playbook`, send `baseRevisionId` on updates, reconcile on `409`).\\n6. If you can run scripts, `node validate-run.mjs <register-file>` checks the register (0 valid, 2 valid but halted, 1 invalid). If you cannot run it, check the rules by hand: one IN_PROGRESS step, earlier steps PASS, later steps PENDING, evidence on every PASS.\\n7. When every step is PASS, post an evidence summary and set the task `done`. If the task has an execution policy, `done` moves it to review or approval: that is expected, not an error.\\n\\n## Run a flow (owner role)\\n\\nOnly the agent whose role is the flow's `owner_role` starts it, and only for a task the Owner has approved.\\n\\n1. Read the flow file. Confirm every item in `inputs` from the task text; if one is missing, ask the Owner in the task and stop.\\n2. Resolve each `role` to an active agent with the team briefing tool (`get-team-briefing`) or the company agent list. If a role has no active agent, mark the run BLOCKED and ask the Owner; never substitute another role silently.\\n3. Write the register in the parent task's `playbook` document, listing every step with its owner.\\n4. Create the steps of the current phase. For each `mode: task` step create a child task: `parentId` = the parent task, the assignee, a title, a description with `done_when`, the evidence required and a link to the parent register, and `blockedByIssueIds` = the child tasks of its `depends_on` steps (status `blocked` if it has blockers, otherwise `todo`). Create in dependency order. For a step with `review`, set the task's `executionPolicy` with a `review` stage whose participant is that reviewer; if the API refuses it for your role, ask the Owner to set it in the task. `mode: checklist` steps stay as lines in the parent register, handled by you.\\n5. Slots (`slots:`) name a role chosen by an earlier step. Create the steps that use a slot only after the choosing step is done: Paperclip wakes you when all current children are terminal, then you create the next phase.\\n6. Paperclip wakes each assignee when its blockers are done and wakes you when all children are done. On each wake, copy the child result into the register as PASS with evidence (or BLOCKED), then continue.\\n7. Close out: check every acceptance check against the evidence, post the summary, and set the parent `done`.\\n\\n## With the Playbook Runner plugin\\n\\nIf the tools `playbook-start-flow`, `playbook-complete-step`, `playbook-review-verdict` and `playbook-status` are available, use them instead of creating tasks by hand. As the owner, pass the flow file's text to `playbook-start-flow`: roles are matched to agents by name or title, and you only pass `assignees` (role \u2192 agent id) for the ones it reports as not found. A step with `approval: owner` needs `ownerApproval` (the reference to the Owner's approval, obtained through the CEO) when you close it; close your checklist steps with `playbook-complete-step` (this also supplies the implementer or channel roles you chose). As a reviewer, give your verdict with `playbook-review-verdict`, never by just setting the review task done. The plugin counts the review rounds and opens the escalation task itself. If you hold an escalation task: when you resolved it, set that task done (a new review cycle starts); when your one attempt failed, call `playbook-escalate` with what you tried, and the case goes to the next level (sector head \u2192 CEO \u2192 Owner).\\n\\n## You were assigned a step of a flow\\n\\nRead your task description and the parent register. Do the work inside the stated scope, record the evidence in a task comment, then set the task `done`. A reviewer may follow because of the task's execution policy; if they request changes, fix what they listed and resubmit. If you cannot finish for a reason outside your control, set the task `blocked` and say what is needed and from whom.\\n\\n## Default delivery checklist\\n\\n1. Confirm the assigned task, scope, acceptance checks, owner, dependencies and latest status.\\n2. Inspect the relevant repository, source material, account evidence or existing deliverable; record material unknowns.\\n3. Write the smallest complete plan with assumptions, risks, ordered actions and the evidence you will provide.\\n4. Do the role work in scope and preserve established sources of truth.\\n5. Check each acceptance item against evidence; list gaps, unavailable checks and blockers.\\n6. Attach evidence and hand off in Paperclip; update only your own task.\\n\\n## What is and is not enforced\\n\\n- Enforced by Paperclip: a blocked task does not start until its blockers are done; the parent is woken when its children finish; an execution policy turns `done` into review/approval.\\n- Not enforced: the register is advisory text, and the assignee still sets `done`. Use a review stage wherever evidence must be checked by someone else.\\n\\n## Review loop and escalation\\n\\nEach sector resolves its own work. The Owner assigns to the CEO, the CEO to the sector head (CTO, marketing director, COO, sales lead), the sector head to the team. Escalation moves up one level at a time:\\n\\n1. **Team.** A reviewer in the same sector (for development, QA reviews the implementer) who finds defects uses *request changes* with a concrete list of what fails and how it was seen. The task returns to its producer, who fixes and resubmits. Keep a round counter in the task's `playbook` document or parent register (`round N of 3`); do not rely on Paperclip to count.\\n2. **Sector head.** After the third rejected round, the reviewer stops the loop, wakes the sector head with the defect list and the three rounds' history. The head gets one resolution attempt: change approach, reassign, reduce scope or rewrite the plan, then restarts the loop with the counter reset to 1.\\n3. **CEO.** If the head cannot unblock it, the head hands the CEO what was tried at each level. The CEO gets one attempt.\\n4. **Owner.** Only if the CEO also cannot unblock it, the CEO reports a block to the Owner: what was asked, what each level tried, what decision or resource is missing.\\n\\nA step with `via: ceo` belongs to another sector: do not assign it across sectors yourself. Create it as a task for the CEO, who routes it to the right sector head and reports back. Steps in a flow that are independent of each other run in parallel; steps that depend on another stay chained with blockers. The level order is advisory text, not enforced by Paperclip: say clearly in the task comment at each hand-up who is now responsible.\\n\\n## Stop and escalate to the Owner immediately\\n\\nSpending, publication, hiring, permission changes, production access, legal or safety exposure and irreversible decisions go to the human Owner (through the CEO) without waiting for the loop above. A flow never grants a tool permission or an approval that is not recorded in Paperclip.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n- https://docs.paperclip.ing/guides/projects-workflow/routines/\\n\"}]}", "import type { PaperclipPluginManifestV1 } from \"@paperclipai/plugin-sdk\";\nimport skill from \"./generated/skill.json\" with { type: \"json\" };\n\nexport const PLUGIN_ID = \"paperclipai.playbook-runner\";\n\nconst manifest: PaperclipPluginManifestV1 = {\n  id: PLUGIN_ID,\n  apiVersion: 1,\n  version: \"0.3.2\",\n  displayName: \"Agents & Workflows\",\n  description: \"Runs agent-static flows: creates the child tasks of each phase, chains review tasks, counts review rounds, and escalates a loop that does not converge to the sector head.\",\n  author: \"Local development plugin\",\n  categories: [\"automation\", \"ui\"],\n  capabilities: [\n    \"issues.read\",\n    \"agents.read\",\n    \"agent.sessions.create\",\n    \"agent.sessions.send\",\n    \"agent.sessions.close\",\n    \"http.outbound\",\n    \"issues.create\",\n    \"issues.update\",\n    \"issue.relations.write\",\n    \"issue.comments.create\",\n    \"issue.documents.read\",\n    \"issue.documents.write\",\n    \"plugin.state.read\",\n    \"plugin.state.write\",\n    \"events.subscribe\",\n    \"agent.tools.register\",\n    \"skills.managed\",\n    \"ui.sidebar.register\",\n    \"ui.page.register\",\n  ],\n  entrypoints: { worker: \"./dist/worker.js\", ui: \"./dist/ui\" },\n  ui: { slots: [\n    { type: \"sidebar\", id: \"playbook-sidebar\", displayName: \"Agents & Workflows\", exportName: \"PlaybookSidebar\", order: 99 },\n    { type: \"page\", id: \"playbook-page\", displayName: \"Agents & Workflows\", exportName: \"PlaybookPage\", routePath: \"agents-workflows\" },\n  ] },\n  skills: skill.skills.map((s) => ({ skillKey: s.slug, displayName: s.title, slug: s.slug, description: String(s.description).replace(/\\s+/g, \" \").trim().slice(0, 300), markdown: s.markdown })),\n  tools: [\n    {\n      name: \"playbook-start-flow\",\n      displayName: \"Start a playbook flow\",\n      description: \"Owner of a flow only. Instantiates a flow file (PLAYBOOKS/flows/*.yaml) on the parent task: creates the child tasks of the first phase, the review tasks and the run register document.\",\n      parametersSchema: {\n        type: \"object\",\n        properties: {\n          parentIssueId: { type: \"string\" },\n          flowKey: { type: \"string\" },\n          flowYaml: { type: \"string\" },\n          assignees: { type: \"object\", additionalProperties: { type: \"string\" } },\n          slotChoices: { type: \"object\", additionalProperties: { type: \"array\", items: { type: \"string\" } } },\n          includeOptional: { type: \"array\", items: { type: \"string\" } },\n          outcome: { type: \"string\" },\n          approval: { type: \"string\" },\n        },\n        required: [\"parentIssueId\"],\n      },\n    },\n    {\n      name: \"playbook-complete-step\",\n      displayName: \"Complete a checklist step of a flow\",\n      description: \"Owner of a flow only. Marks one of your own checklist steps done with evidence and creates whatever becomes ready. Also supplies slot choices or missing assignees.\",\n      parametersSchema: {\n        type: \"object\",\n        properties: {\n          parentIssueId: { type: \"string\" },\n          stepId: { type: \"string\" },\n          evidence: { type: \"string\" },\n          ownerApproval: { type: \"string\" },\n          slotChoices: { type: \"object\", additionalProperties: { type: \"array\", items: { type: \"string\" } } },\n          assignees: { type: \"object\", additionalProperties: { type: \"string\" } },\n        },\n        required: [\"parentIssueId\"],\n      },\n    },\n    {\n      name: \"playbook-review-verdict\",\n      displayName: \"Give the verdict on a review task\",\n      description: \"Reviewer only. approve closes the step; changes sends the work back with your defect list, and after the maximum rounds the step is escalated to the sector head.\",\n      parametersSchema: {\n        type: \"object\",\n        properties: {\n          reviewIssueId: { type: \"string\" },\n          verdict: { type: \"string\", enum: [\"approve\", \"changes\"] },\n          defects: { type: \"string\" },\n        },\n        required: [\"reviewIssueId\", \"verdict\"],\n      },\n    },\n    {\n      name: \"playbook-escalate\",\n      displayName: \"Hand an escalation up one level\",\n      description: \"Holder of an escalation task only, after your one resolution attempt failed. Hands the case to the next level (sector head -> CEO -> Owner) with what you tried.\",\n      parametersSchema: { type: \"object\", properties: { escalationIssueId: { type: \"string\" }, tried: { type: \"string\" } }, required: [\"escalationIssueId\", \"tried\"] },\n    },\n    {\n      name: \"playbook-status\",\n      displayName: \"Show the register of a running flow\",\n      description: \"Returns the run register and per-step state of the flow running on a parent task.\",\n      parametersSchema: { type: \"object\", properties: { parentIssueId: { type: \"string\" } }, required: [\"parentIssueId\"] },\n    },\n  ],\n};\n\nexport default manifest;\n"],
+  "sourcesContent": ["{\"skills\":[{\"slug\":\"executive-task-orchestration\",\"title\":\"Executive task orchestration\",\"description\":\"Use when converting owner-approved company priorities into a Paperclip plan, choosing task owners, delegating work, or reviewing cross-team outcomes. Do not use to approve the CEO agent's own consequential actions.\",\"markdown\":\"---\\nname: executive-task-orchestration\\ndescription: >\\n  Use when converting owner-approved company priorities into a Paperclip plan, choosing task owners, delegating work, or reviewing cross-team outcomes. Do not use to approve the CEO agent's own consequential actions.\\n---\\n\\n# Executive task orchestration\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read company goals, existing Paperclip tasks, evidence, and current capacity.\\n2. Separate conversation from tracked work; create no task unless requested or authorized.\\n3. Define outcome, one owner, acceptance evidence, assumptions, dependencies, and human approval needs.\\n4. Delegate bounded work through linked tasks and review evidence before summarizing the outcome.\\n\\n## Expected result\\n\\nA concise priority decision, owner-assigned task plan, approval request, or evidence-backed closeout.\\n\\n## Stop and escalate\\n\\nEscalate budget, publication, hiring, production access, legal or safety exposure, and irreversible decisions to the human Owner.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/org/org-structure/\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n\"},{\"slug\":\"marketing-campaign-planning\",\"title\":\"Marketing campaign planning\",\"description\":\"Use when defining a campaign objective, audience, offer, positioning, message, channel mix, measurement, or campaign review. Do not use this skill to publish, spend, or promise results.\",\"markdown\":\"---\\nname: marketing-campaign-planning\\ndescription: >\\n  Use when defining a campaign objective, audience, offer, positioning, message, channel mix, measurement, or campaign review. Do not use this skill to publish, spend, or promise results.\\n---\\n\\n# Marketing campaign planning\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read COMPANY.md and BUSINESS.md and identify approved goals, audiences, proof, constraints, and voice.\\n2. Use current research to define one audience problem, offer, message, and measurable conversion.\\n3. Choose channels, owners, budget request, dates, dependencies, and stop criteria.\\n4. Review evidence against targets and recommend continue, revise, or stop.\\n\\n## Expected result\\n\\nA campaign brief with objective, audience, offer, evidence, message, channels, owners, measures, budget request, risks, approvals, and review date.\\n\\n## Stop and escalate\\n\\nDo not invent testimonials, results, audience evidence, or legal claims; seek human approval for budget and publication.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"technical-architecture-and-delegation\",\"title\":\"Technical architecture and delegation\",\"description\":\"Use when a development request needs technical discovery, stack selection, architecture decisions, a fullstack-versus-split decision, or developer assignments. Do not use to make unapproved production changes.\",\"markdown\":\"---\\nname: technical-architecture-and-delegation\\ndescription: >\\n  Use when a development request needs technical discovery, stack selection, architecture decisions, a fullstack-versus-split decision, or developer assignments. Do not use to make unapproved production changes.\\n---\\n\\n# Technical architecture and delegation\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect repository instructions, stack and versions, interfaces, data, deployment path, and constraints.\\n2. Define the smallest architecture that meets the approved outcome.\\n3. Choose one implementation owner or split work only when interfaces are stable and risk justifies it.\\n4. Write acceptance checks, security and privacy requirements, dependencies, test evidence, and release conditions.\\n\\n## Expected result\\n\\nA short technical decision record and implementation plan with named owners, interfaces, risks, and verification evidence.\\n\\n## Stop and escalate\\n\\nEscalate unknown production access, regulated data, security findings, major migrations, and infrastructure spend to the human Owner.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/org/org-structure/\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n\"},{\"slug\":\"n8n-workflow-design-and-operations\",\"title\":\"n8n workflow design and operations\",\"description\":\"Use when assessing, designing, implementing, testing, or handing off an approved n8n automation or MCP-exposed workflow.\",\"markdown\":\"---\\nname: n8n-workflow-design-and-operations\\ndescription: >\\n  Use when assessing, designing, implementing, testing, or handing off an approved n8n automation or MCP-exposed workflow.\\n---\\n\\n# n8n workflow design and operations\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm the CEO-selected approach, workflow owner, company instance, permitted data, and task acceptance criteria.\\n2. Map triggers, inputs, data movement, side effects, credentials, retries, idempotency, and failure handling before building.\\n3. Build the smallest maintainable workflow in a development or test environment; keep complex reusable business logic in versioned code where that improves testability.\\n4. Test expected, malformed, duplicate, timeout, rate-limit, and partial-failure cases and preserve redacted execution evidence.\\n5. Document monitoring, alerting, recovery, rollback, credential ownership, and human approval required before production activation.\\n\\n## Expected result\\n\\nA workflow design or handoff with owner, version, environment, data flow, integrations, test evidence, residual risks, monitoring, recovery, and approval state.\\n\\n## Stop and escalate\\n\\nStop before production activation, external messaging, destructive changes, or access to another company's data unless the assigned task and authorized human approval explicitly permit the action. Never expose secrets or unnecessary personal data.\\n\\n## References\\n\\n- https://docs.n8n.io/connect/connect-to-n8n-mcp-server/\\n- https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/\\n- https://docs.n8n.io/hosting/security/\\n\"},{\"slug\":\"operating-cadence-and-handoffs\",\"title\":\"Operating cadence and handoffs\",\"description\":\"Use when preparing a daily or weekly operating brief, coordinating cross-team dependencies, or diagnosing recurring workflow friction. Do not use to change company strategy or make external commitments.\",\"markdown\":\"---\\nname: operating-cadence-and-handoffs\\ndescription: >\\n  Use when preparing a daily or weekly operating brief, coordinating cross-team dependencies, or diagnosing recurring workflow friction. Do not use to change company strategy or make external commitments.\\n---\\n\\n# Operating cadence and handoffs\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read only approved priorities, task statuses, deadlines, and permitted service summaries.\\n2. Separate evidence, estimates, blockers, and owner decisions.\\n3. Rank the three most material actions and name one accountable owner for each.\\n4. Record dependencies, escalation routes, and a review date for any proposed process pilot.\\n\\n## Expected result\\n\\nAn owner-ready operating brief or handoff with status, priorities, accountable owners, evidence, and decisions required.\\n\\n## Stop and escalate\\n\\nDo not message customers, move money, reassign work against the reporting tree, or expose unnecessary personal data.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/org/org-structure/\\n- https://docs.paperclip.ing/guides/projects-workflow/routines/\\n\"},{\"slug\":\"qa-and-release\",\"title\":\"Risk-based QA and release\",\"description\":\"Use when planning tests, validating acceptance criteria, checking regressions, or preparing release evidence for a software change. Do not treat passing tests as proof of zero risk.\",\"markdown\":\"---\\nname: qa-and-release\\ndescription: >\\n  Use when planning tests, validating acceptance criteria, checking regressions, or preparing release evidence for a software change. Do not treat passing tests as proof of zero risk.\\n---\\n\\n# Risk-based QA and release\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Map each acceptance criterion to a reproducible check.\\n2. Prioritize user journeys, data boundaries, failure states, integrations, and supported versions by risk.\\n3. Run authorized local or staging checks and preserve commands, results, and defects.\\n4. Review unresolved findings, migration safety, monitoring, backup, rollback, and required approvals.\\n\\n## Expected result\\n\\nA risk-based test plan, reproducible findings, coverage limits, and release recommendation.\\n\\n## Stop and escalate\\n\\nBlock release recommendation for unresolved critical findings, missing authorization, or absent recovery evidence.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/agent-developer/writing-a-skill/\\n- https://github.com/microsoft/playwright-mcp\\n\"},{\"slug\":\"customer-care-triage\",\"title\":\"Customer care triage\",\"description\":\"Use when classifying customer messages, answering approved routine questions, preparing a support reply, or escalating a complaint or sensitive case. Do not provide unapproved legal, medical, safety, or financial advice.\",\"markdown\":\"---\\nname: customer-care-triage\\ndescription: >\\n  Use when classifying customer messages, answering approved routine questions, preparing a support reply, or escalating a complaint or sensitive case. Do not provide unapproved legal, medical, safety, or financial advice.\\n---\\n\\n# Customer care triage\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Check the company support policy, approved answer source, queue permissions, and response authority.\\n2. Classify intent, urgency, sensitivity, and responsible service owner.\\n3. Use only current approved facts; draft when send authority is absent.\\n4. Route uncertain or sensitive requests to a named human or qualified professional and record a minimized handoff.\\n\\n## Expected result\\n\\nA categorized queue item, approved answer or draft, or clear escalation with next action and owner.\\n\\n## Stop and escalate\\n\\nNever promise a legal, medical, refund, compliance, or commercial outcome. Minimize personal data and escalate potential harm or formal complaints.\\n\\n## References\\n\\n- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679\\n\"},{\"slug\":\"market-and-competitor-research\",\"title\":\"Market and competitor research\",\"description\":\"Use when investigating an audience, market opportunity, competitor offer, pricing, demand signal, or channel pattern. Do not present estimates as verified facts or infer private data.\",\"markdown\":\"---\\nname: market-and-competitor-research\\ndescription: >\\n  Use when investigating an audience, market opportunity, competitor offer, pricing, demand signal, or channel pattern. Do not present estimates as verified facts or infer private data.\\n---\\n\\n# Market and competitor research\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Define the decision the research must support and the permitted sources.\\n2. Collect dated evidence about customer needs, competitor offers, pricing, positioning, and channel presence.\\n3. Separate observations, estimates, and hypotheses; record source, method, freshness, and confidence.\\n4. Synthesize opportunity, counter-evidence, unknowns, and what should be tested next.\\n\\n## Expected result\\n\\nA concise source-linked research brief with evidence, limitations, opportunity hypotheses, and next validation step.\\n\\n## Stop and escalate\\n\\nDo not use restricted sources, infer sensitive traits, or claim market size or demand without a traceable method.\\n\\n## References\\n\\n- https://support.google.com/trends/answer/4365533\\n- https://github.com/HubSpot/agent-cli-skills\\n\"},{\"slug\":\"brand-positioning-and-creative-brief\",\"title\":\"Brand positioning and creative brief\",\"description\":\"Use when turning approved customer evidence into positioning, a campaign angle, creative direction, or a brief for visual assets. Do not invent company proof or change approved brand commitments.\",\"markdown\":\"---\\nname: brand-positioning-and-creative-brief\\ndescription: >\\n  Use when turning approved customer evidence into positioning, a campaign angle, creative direction, or a brief for visual assets. Do not invent company proof or change approved brand commitments.\\n---\\n\\n# Brand positioning and creative brief\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read approved company voice, offers, proof, and audience context.\\n2. Translate research into a customer problem, differentiated value, reason to believe, and message hierarchy.\\n3. Define creative concept, format, audience, placement, accessibility, and claim limits.\\n4. Present alternatives and evidence for owner review before production or publication.\\n\\n## Expected result\\n\\nA positioning statement and creative brief with audience, insight, promise, support, concept, format, and review needs.\\n\\n## Stop and escalate\\n\\nFlag unsupported claims, sensitive imagery, unclear rights, and any material change to brand promises.\\n\\n## References\\n\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"content-strategy-planning\",\"title\":\"Content strategy planning\",\"description\":\"Use when planning an editorial series, content calendar, audience education sequence, or reusable campaign content. Do not create volume without an audience need and measurable purpose.\",\"markdown\":\"---\\nname: content-strategy-planning\\ndescription: >\\n  Use when planning an editorial series, content calendar, audience education sequence, or reusable campaign content. Do not create volume without an audience need and measurable purpose.\\n---\\n\\n# Content strategy planning\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Start from approved audience questions, campaign objective, and source material.\\n2. Choose content themes, formats, channel roles, sequence, and an intended audience action.\\n3. Assign source checks, specialist review, voice review, owner, and publication date.\\n4. Define success measures and reuse rules before the content is produced.\\n\\n## Expected result\\n\\nAn editorial brief or calendar with themes, audience intent, formats, owners, sources, reviewers, and measures.\\n\\n## Stop and escalate\\n\\nPause on unsupported factual claims, regulated topics without qualified review, or reuse of identifiable customer stories without consent.\\n\\n## References\\n\\n- https://developers.google.com/search/docs/fundamentals/creating-helpful-content\\n\"},{\"slug\":\"evidence-based-copywriting\",\"title\":\"Evidence-based copywriting\",\"description\":\"Use when drafting or revising customer-facing marketing copy, a landing page, offer, advertisement, or email. Do not fabricate proof, urgency, scarcity, or guaranteed outcomes.\",\"markdown\":\"---\\nname: evidence-based-copywriting\\ndescription: >\\n  Use when drafting or revising customer-facing marketing copy, a landing page, offer, advertisement, or email. Do not fabricate proof, urgency, scarcity, or guaranteed outcomes.\\n---\\n\\n# Evidence-based copywriting\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read the approved voice, offer, audience, and evidence in company context.\\n2. Identify the audience problem, single promise, reason to believe, and next action.\\n3. Draft plainly with claims tied to named evidence and limits.\\n4. Check clarity, accessibility, channel fit, required review, and approval before publication.\\n\\n## Expected result\\n\\nA copy draft with audience, purpose, source notes for factual claims, CTA, and open approvals.\\n\\n## Stop and escalate\\n\\nEscalate health, safety, legal, financial, comparative, quantified, or testimonial claims for documented review.\\n\\n## References\\n\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"seo-audit-and-search-content\",\"title\":\"SEO audit and search content\",\"description\":\"Use when diagnosing organic-search visibility, prioritizing an SEO issue, or preparing a search-focused content brief. Do not promise rankings or use manipulative tactics.\",\"markdown\":\"---\\nname: seo-audit-and-search-content\\ndescription: >\\n  Use when diagnosing organic-search visibility, prioritizing an SEO issue, or preparing a search-focused content brief. Do not promise rankings or use manipulative tactics.\\n---\\n\\n# SEO audit and search content\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Check the site's technical and content context and identify the target user intent.\\n2. Use permitted Search Console or analytics evidence; distinguish query data from guesses.\\n3. Prioritize crawl, index, performance, accessibility, and content-quality issues by impact and confidence.\\n4. Write a change brief with current state, recommended action, validation evidence, and review date.\\n\\n## Expected result\\n\\nA prioritized SEO issue list or content brief with evidence and validation steps.\\n\\n## Stop and escalate\\n\\nDo not create doorway pages, mass-generated thin content, fake backlinks, or unsupported structured data.\\n\\n## References\\n\\n- https://developers.google.com/search/docs/fundamentals/creating-helpful-content\\n- https://developers.google.com/search/docs/crawling-indexing\\n\"},{\"slug\":\"paid-media-testing\",\"title\":\"Paid media testing\",\"description\":\"Use when designing, reviewing, or analyzing a paid advertising test. Do not launch ads, change bids, or spend budget without explicit authorization.\",\"markdown\":\"---\\nname: paid-media-testing\\ndescription: >\\n  Use when designing, reviewing, or analyzing a paid advertising test. Do not launch ads, change bids, or spend budget without explicit authorization.\\n---\\n\\n# Paid media testing\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm approved offer, audience, destination, budget envelope, and claim evidence.\\n2. Define campaign structure, conversion event, exclusions, creative variants, and tracking checks.\\n3. Set baseline, success threshold, stop rule, review window, and accountable human approver.\\n4. Analyze results with spend, qualified outcomes, attribution limits, and risks stated separately.\\n\\n## Expected result\\n\\nAn approval-ready test plan or evidence-based performance report.\\n\\n## Stop and escalate\\n\\nStop on tracking failure, unapproved claims, spend-limit uncertainty, audience-policy risk, or unapproved account changes.\\n\\n## References\\n\\n- https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server/\\n- https://github.com/google/agent-skills\\n\"},{\"slug\":\"social-channel-operations\",\"title\":\"Organic social channel operations\",\"description\":\"Use when adapting approved campaign material to social channels, planning a publishing schedule, or preparing moderation guidance. Do not publish or engage in disputes without authorization.\",\"markdown\":\"---\\nname: social-channel-operations\\ndescription: >\\n  Use when adapting approved campaign material to social channels, planning a publishing schedule, or preparing moderation guidance. Do not publish or engage in disputes without authorization.\\n---\\n\\n# Organic social channel operations\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm channel, audience, campaign objective, source facts, and approved voice.\\n2. Adapt one idea to the platform's format without changing its evidence or promise.\\n3. Prepare accessible assets, caption, CTA, alt text, timing, and moderation route.\\n4. Submit drafts for approval and record performance or recurring audience questions.\\n\\n## Expected result\\n\\nA channel-ready draft pack and schedule with sources, owner, moderation plan, and approval status.\\n\\n## Stop and escalate\\n\\nEscalate complaints, legal threats, sensitive disclosures, harassment, misinformation risk, or unclear response authority.\\n\\n## References\\n\\n- https://github.com/anthropics/skills/tree/main/skills/internal-comms\\n\"},{\"slug\":\"lifecycle-email-campaigns\",\"title\":\"Lifecycle email campaigns\",\"description\":\"Use when drafting a consent-based onboarding, lifecycle, retention, or customer update email sequence. Do not send to a list without approved audience basis and suppression checks.\",\"markdown\":\"---\\nname: lifecycle-email-campaigns\\ndescription: >\\n  Use when drafting a consent-based onboarding, lifecycle, retention, or customer update email sequence. Do not send to a list without approved audience basis and suppression checks.\\n---\\n\\n# Lifecycle email campaigns\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm audience source, communication purpose, legal basis or consent policy, and suppression rules.\\n2. Map the sequence to a customer lifecycle need and one clear action per message.\\n3. Draft subject, body, sender, preference and unsubscribe handling, and tracking.\\n4. Review claims, deliverability, segmentation, and approval before sending; measure meaningful outcomes.\\n\\n## Expected result\\n\\nAn email sequence brief or draft set with audience rules, timing, suppression, approval, and measures.\\n\\n## Stop and escalate\\n\\nStop if contact permission, opt-out handling, sender identity, or sensitive segmentation is unclear.\\n\\n## References\\n\\n- https://developers.google.com/workspace/guides/configure-mcp-servers\\n\"},{\"slug\":\"marketing-measurement\",\"title\":\"Marketing measurement and analysis\",\"description\":\"Use when defining campaign events, checking tracking, analyzing funnel performance, or preparing a marketing report. Do not change campaigns, budgets, or landing pages based on analysis alone.\",\"markdown\":\"---\\nname: marketing-measurement\\ndescription: >\\n  Use when defining campaign events, checking tracking, analyzing funnel performance, or preparing a marketing report. Do not change campaigns, budgets, or landing pages based on analysis alone.\\n---\\n\\n# Marketing measurement and analysis\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm objective, metric definitions, reporting period, data source, and known attribution limits.\\n2. Check event coverage and data quality before comparing results.\\n3. Analyze funnel stages with denominators, segments, and uncertainty visible.\\n4. Explain supported findings and recommend a test or decision for the accountable owner.\\n\\n## Expected result\\n\\nA measurement plan, source-linked analysis, or decision brief with definitions, limitations, and next action.\\n\\n## Stop and escalate\\n\\nDo not infer personal behavior beyond authorized aggregation or make causal claims from descriptive data alone.\\n\\n## References\\n\\n- https://developers.google.com/analytics/devguides/MCP\\n- https://posthog.com/docs/model-context-protocol\\n\"},{\"slug\":\"leadgen-strategy-and-funnel\",\"title\":\"Lead generation strategy and funnel\",\"description\":\"Use when defining an ideal customer segment, acquisition funnel, qualification criteria, channel test, or handoff to Sales. Do not maximize raw lead volume without fit and contact safeguards.\",\"markdown\":\"---\\nname: leadgen-strategy-and-funnel\\ndescription: >\\n  Use when defining an ideal customer segment, acquisition funnel, qualification criteria, channel test, or handoff to Sales. Do not maximize raw lead volume without fit and contact safeguards.\\n---\\n\\n# Lead generation strategy and funnel\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read approved offer, market evidence, privacy boundaries, and Sales acceptance criteria.\\n2. Define target segment, observable intent signals, exclusions, and conversion event.\\n3. Select a bounded channel experiment with source, cost/effort limit, and stop rule.\\n4. Agree qualification fields and handoff timing with the Sales owner; measure quality through the funnel.\\n\\n## Expected result\\n\\nA segment and funnel brief with qualification, contact rules, channel test, owner, measures, and handoff.\\n\\n## Stop and escalate\\n\\nEscalate unclear contact basis, sensitive profiling, purchased lists, or unsupported targeting data.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server\\n\"},{\"slug\":\"prospect-research-and-data-quality\",\"title\":\"Prospect research and data quality\",\"description\":\"Use when researching or cleaning a business prospect list for an approved purpose. Do not infer sensitive personal traits or treat public data as permission to contact.\",\"markdown\":\"---\\nname: prospect-research-and-data-quality\\ndescription: >\\n  Use when researching or cleaning a business prospect list for an approved purpose. Do not infer sensitive personal traits or treat public data as permission to contact.\\n---\\n\\n# Prospect research and data quality\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm research purpose, allowed sources, minimum fields, and contact policy.\\n2. Capture source, retrieval date, freshness, and confidence for important fields.\\n3. Check relevance, duplicates, exclusions, and conflicting information.\\n4. Return only necessary fields and document records removed or needing human review.\\n\\n## Expected result\\n\\nA source-linked prospect or segment evidence table with quality flags and permitted handoff fields.\\n\\n## Stop and escalate\\n\\nDo not scrape restricted sites, fabricate contact details, or export data without approved use and access.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679\\n\"},{\"slug\":\"outreach-campaign-operations\",\"title\":\"Outreach campaign operations\",\"description\":\"Use when preparing an approved outbound outreach sequence, audience rules, or campaign results report. Do not send messages or bypass suppression and opt-out controls.\",\"markdown\":\"---\\nname: outreach-campaign-operations\\ndescription: >\\n  Use when preparing an approved outbound outreach sequence, audience rules, or campaign results report. Do not send messages or bypass suppression and opt-out controls.\\n---\\n\\n# Outreach campaign operations\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Verify approved offer, list source, contact basis, segment, and exclusions.\\n2. Draft concise, relevant messages with honest personalization and a clear next step.\\n3. Check suppression, opt-out, frequency, sender, and CRM handoff rules.\\n4. Submit for approval; after authorized launch, report replies, qualified outcomes, complaints, and opt-outs.\\n\\n## Expected result\\n\\nAn outreach draft pack and launch checklist, or a campaign results and stop recommendation.\\n\\n## Stop and escalate\\n\\nPause on unclear permission, complaints, misleading claims, sensitive data, or missing unsubscribe handling.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server\\n\"},{\"slug\":\"administrative-operations-coordination\",\"title\":\"Administrative operations coordination\",\"description\":\"Use when converting internal decisions into action logs, coordinating administrative requests, or preparing routine operating records. Do not commit funds, sign agreements, or send external messages without approval.\",\"markdown\":\"---\\nname: administrative-operations-coordination\\ndescription: >\\n  Use when converting internal decisions into action logs, coordinating administrative requests, or preparing routine operating records. Do not commit funds, sign agreements, or send external messages without approval.\\n---\\n\\n# Administrative operations coordination\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm requester, purpose, due date, source record, and approving owner.\\n2. Separate decisions from discussion and assign one owner per action.\\n3. Prepare a reversible draft, calendar entry, or checklist using approved systems.\\n4. Record approval, completion evidence, and unresolved items in the source of truth.\\n\\n## Expected result\\n\\nA clear action record, request route, deadline list, or approval-ready administrative draft.\\n\\n## Stop and escalate\\n\\nEscalate legal, financial, access, privacy, and regulated-record decisions to their named owner.\\n\\n## References\\n\\n- https://developers.google.com/workspace/guides/configure-mcp-servers\\n\"},{\"slug\":\"finance-administration-review\",\"title\":\"Finance administration review\",\"description\":\"Use when reconciling source records, preparing invoice status, checking finance totals, or drafting an approval-ready payment pack. Do not execute payments or provide tax or accounting advice.\",\"markdown\":\"---\\nname: finance-administration-review\\ndescription: >\\n  Use when reconciling source records, preparing invoice status, checking finance totals, or drafting an approval-ready payment pack. Do not execute payments or provide tax or accounting advice.\\n---\\n\\n# Finance administration review\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm reporting period, currency, accounting owner, and authoritative source records.\\n2. Reconcile totals and preserve references to source documents.\\n3. Separate actuals, estimates, forecasts, and assumptions; explain variances.\\n4. Prepare proposed actions for review and record the human decision.\\n\\n## Expected result\\n\\nA traceable reconciliation, invoice list, variance note, or approval-ready finance pack.\\n\\n## Stop and escalate\\n\\nEscalate missing evidence, unusual payment changes, tax judgments, bank-detail changes, and payment execution.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n\"},{\"slug\":\"records-and-document-control\",\"title\":\"Records and document control\",\"description\":\"Use when maintaining a document register, checking versions and approvals, or preparing a controlled record for sharing. Do not delete records or invent retention periods.\",\"markdown\":\"---\\nname: records-and-document-control\\ndescription: >\\n  Use when maintaining a document register, checking versions and approvals, or preparing a controlled record for sharing. Do not delete records or invent retention periods.\\n---\\n\\n# Records and document control\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm record owner, authoritative location, purpose, sensitivity, and access scope.\\n2. Check version, approval status, date, and duplicate or stale copies.\\n3. Apply the approved naming and filing convention while preserving the source.\\n4. Record missing records, access questions, or retention decisions for the authorized owner.\\n\\n## Expected result\\n\\nAn evidence index, document inventory, version history, or minimized sharing proposal.\\n\\n## Stop and escalate\\n\\nEscalate legal holds, health or case records, deletion, external sharing, and retention changes.\\n\\n## References\\n\\n- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679\\n\"},{\"slug\":\"sales-pipeline-management\",\"title\":\"Sales pipeline management\",\"description\":\"Use when defining sales stages, reviewing pipeline quality, preparing a forecast, or improving the lead handoff from Marketing. Do not invent forecast certainty or change approved prices.\",\"markdown\":\"---\\nname: sales-pipeline-management\\ndescription: >\\n  Use when defining sales stages, reviewing pipeline quality, preparing a forecast, or improving the lead handoff from Marketing. Do not invent forecast certainty or change approved prices.\\n---\\n\\n# Sales pipeline management\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Confirm approved offers, stage definitions, decision roles, and the reporting period.\\n2. Check stage evidence, next action, owner, value, and close conditions.\\n3. Identify stalled, unsupported, duplicate, or no-fit opportunities.\\n4. Summarize supported pipeline ranges, assumptions, handoffs, and owner decisions.\\n\\n## Expected result\\n\\nA stage definition, pipeline review, forecast range, and next-step owner list.\\n\\n## Stop and escalate\\n\\nEscalate pricing, contractual terms, claims, customer data access, and unsupported forecast assumptions.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n\"},{\"slug\":\"sales-lead-qualification\",\"title\":\"Sales lead qualification\",\"description\":\"Use when responding to a new enquiry, preparing discovery questions, or deciding whether a prospect meets approved fit and intent criteria. Do not pressure or mislead a buyer.\",\"markdown\":\"---\\nname: sales-lead-qualification\\ndescription: >\\n  Use when responding to a new enquiry, preparing discovery questions, or deciding whether a prospect meets approved fit and intent criteria. Do not pressure or mislead a buyer.\\n---\\n\\n# Sales lead qualification\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Check approved offer, qualification rules, response-time expectations, and contact history.\\n2. Ask only relevant questions about need, context, timing, decision process, and fit.\\n3. Record facts and direct quotes separately from hypotheses.\\n4. Route qualified prospects to the right seller and provide a clear next step or respectful no-fit response.\\n\\n## Expected result\\n\\nA concise qualification record, discovery brief, follow-up draft, or reasoned no-fit outcome.\\n\\n## Stop and escalate\\n\\nEscalate sensitive, regulated, legal, clinical, financial, or complaint-related enquiries.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n\"},{\"slug\":\"consultative-sales-proposals\",\"title\":\"Consultative sales proposals\",\"description\":\"Use when preparing a discovery summary, proposal, objection response, or customer follow-up for an approved offer. Do not promise outcomes outside the approved scope.\",\"markdown\":\"---\\nname: consultative-sales-proposals\\ndescription: >\\n  Use when preparing a discovery summary, proposal, objection response, or customer follow-up for an approved offer. Do not promise outcomes outside the approved scope.\\n---\\n\\n# Consultative sales proposals\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Summarize the buyer's stated problem, decision criteria, and desired outcome.\\n2. Match needs to an approved offer and identify gaps or exclusions.\\n3. Draft scope, deliverables, price source, assumptions, timing, and responsibilities.\\n4. Request human approval before sending and record the customer's decision and next step.\\n\\n## Expected result\\n\\nAn evidence-based discovery note, proposal draft, or buyer decision plan.\\n\\n## Stop and escalate\\n\\nDo not invent discounts, deadlines, guarantees, legal conclusions, or product capabilities.\\n\\n## References\\n\\n- https://github.com/HubSpot/agent-cli-skills\\n- https://www.agcm.it/per-i-consumatori/le-pratiche-commerciali-scorrette-e-la-pubblicit-ingannevole/\\n\"},{\"slug\":\"engineering-delivery-baseline\",\"title\":\"Engineering delivery baseline\",\"description\":\"Use for software implementation tasks across Next.js, MEAN, and WordPress repositories. Do not use to bypass repository instructions, tests, security review, or task approval.\",\"markdown\":\"---\\nname: engineering-delivery-baseline\\ndescription: >\\n  Use for software implementation tasks across Next.js, MEAN, and WordPress repositories. Do not use to bypass repository instructions, tests, security review, or task approval.\\n---\\n\\n# Engineering delivery baseline\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect the repository's instructions, existing patterns, versions, and relevant tests before changing files.\\n2. Restate the acceptance criteria and make the smallest scoped change.\\n3. Use authorized checks that match the task risk and project conventions; record commands and results.\\n4. Review the final diff for scope, security, regressions, documentation, and a clear handoff.\\n\\n## Expected result\\n\\nA scoped implementation with acceptance evidence, known limitations, and reviewer-ready change summary.\\n\\n## Stop and escalate\\n\\nDo not expose secrets, write production data, change unrelated architecture, or claim a check passed when it was not run.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/agent-developer/writing-a-skill/\\n- https://github.com/github/github-mcp-server\\n\"},{\"slug\":\"nextjs-development\",\"title\":\"Next.js development\",\"description\":\"Use when implementing or reviewing a Next.js feature, route, server action, API boundary, rendering behavior, or performance issue. Do not assume a router, runtime, cache, or Next.js version.\",\"markdown\":\"---\\nname: nextjs-development\\ndescription: >\\n  Use when implementing or reviewing a Next.js feature, route, server action, API boundary, rendering behavior, or performance issue. Do not assume a router, runtime, cache, or Next.js version.\\n---\\n\\n# Next.js development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Read package manifests and repository guidance to identify Next.js version, App/Pages Router, runtime, and test setup.\\n2. Keep server-only secrets and privileged logic out of client bundles.\\n3. Follow the existing data-fetching, caching, authentication, and route patterns.\\n4. Use Next.js DevTools only when the documented version and local development-server prerequisites are met; verify behavior with project checks.\\n\\n## Expected result\\n\\nA version-aligned implementation or review with server/client boundaries and test evidence.\\n\\n## Stop and escalate\\n\\nEscalate new database, authentication, runtime, or deployment choices that exceed task scope.\\n\\n## References\\n\\n- https://nextjs.org/docs/app/guides/ai-agents\\n- https://nextjs.org/docs/app/guides/mcp\\n- https://github.com/vercel/next.js/tree/canary/skills\\n\"},{\"slug\":\"mean-stack-development\",\"title\":\"MEAN stack development\",\"description\":\"Use when implementing a feature across Angular, Node/Express, and MongoDB, or when working on one of those layers in a MEAN application. Do not assume library versions or production database access.\",\"markdown\":\"---\\nname: mean-stack-development\\ndescription: >\\n  Use when implementing a feature across Angular, Node/Express, and MongoDB, or when working on one of those layers in a MEAN application. Do not assume library versions or production database access.\\n---\\n\\n# MEAN stack development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect Angular, Node, Express, MongoDB, and data-access versions and existing boundaries.\\n2. Define typed API and validation contracts before changing dependent layers.\\n3. Use development data and review schema, index, migration, authorization, and query behavior.\\n4. Run appropriate unit, API, build, and browser checks and document results.\\n\\n## Expected result\\n\\nA coherent layer-specific or vertical-slice change with API, persistence, and UI evidence.\\n\\n## Stop and escalate\\n\\nDo not run destructive operations or production CRUD through MongoDB MCP; escalate schema changes and sensitive data access.\\n\\n## References\\n\\n- https://angular.dev/ai/agent-skills\\n- https://angular.dev/ai/mcp\\n- https://www.mongodb.com/docs/mcp-server/overview/\\n- https://expressjs.com/advanced/best-practice-security/\\n\"},{\"slug\":\"wordpress-site-maintenance\",\"title\":\"WordPress site maintenance\",\"description\":\"Use when diagnosing or maintaining a WordPress site, configuration, integration, upgrade, or migration. Do not edit WordPress core or run unapproved production changes.\",\"markdown\":\"---\\nname: wordpress-site-maintenance\\ndescription: >\\n  Use when diagnosing or maintaining a WordPress site, configuration, integration, upgrade, or migration. Do not edit WordPress core or run unapproved production changes.\\n---\\n\\n# WordPress site maintenance\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Identify WordPress, PHP, hosting, theme, plugin, and deployment versions and the site's existing architecture.\\n2. Reproduce the issue in local or staging and identify the responsible layer.\\n3. Prefer supported APIs, WP-CLI, reversible configuration, and documented migration steps.\\n4. Check backup, compatibility, permissions, performance, accessibility, and rollback evidence.\\n\\n## Expected result\\n\\nA bounded site fix or an upgrade/integration plan with reproducible checks and rollback notes.\\n\\n## Stop and escalate\\n\\nRequire human approval, backup, and rollback for production writes, migrations, credentials, or plugin changes.\\n\\n## References\\n\\n- https://developer.wordpress.org/\\n- https://developer.wordpress.org/cli/commands/\\n\"},{\"slug\":\"wordpress-plugin-development\",\"title\":\"WordPress plugin development\",\"description\":\"Use when designing, implementing, testing, or reviewing a WordPress plugin or custom functional extension. Do not edit WordPress core or third-party plugin source.\",\"markdown\":\"---\\nname: wordpress-plugin-development\\ndescription: >\\n  Use when designing, implementing, testing, or reviewing a WordPress plugin or custom functional extension. Do not edit WordPress core or third-party plugin source.\\n---\\n\\n# WordPress plugin development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Inspect supported WordPress/PHP versions, plugin structure, hooks, APIs, and existing tests.\\n2. Check capabilities and authorization, nonces, validation, sanitization, escaping, and data lifecycle.\\n3. Implement the smallest change using supported extension points.\\n4. Run authorized checks and prepare compatibility, upgrade, security, and release evidence.\\n\\n## Expected result\\n\\nA maintainable plugin change with permission, data, compatibility, test, and release notes.\\n\\n## Stop and escalate\\n\\nEscalate external service calls, sensitive data, destructive migrations, and live-site writes.\\n\\n## References\\n\\n- https://developer.wordpress.org/plugins/\\n- https://developer.wordpress.org/plugins/security/\\n- https://github.com/WordPress/agent-skills\\n\"},{\"slug\":\"wordpress-theme-development\",\"title\":\"WordPress theme development\",\"description\":\"Use when implementing or reviewing a WordPress theme, block theme, template, pattern, theme.json setting, or editor/front-end presentation. Do not put persistent business logic in a theme.\",\"markdown\":\"---\\nname: wordpress-theme-development\\ndescription: >\\n  Use when implementing or reviewing a WordPress theme, block theme, template, pattern, theme.json setting, or editor/front-end presentation. Do not put persistent business logic in a theme.\\n---\\n\\n# WordPress theme development\\n\\nThis is an original, markdown-only Paperclip skill designed for Pi Agent and Claude Code skill discovery. It guides work; it does not grant access, decide approvals, or replace the role's immutable playbook.\\n\\n## Before starting\\n\\n- Read the assigned role instructions, COMPANY.md, BUSINESS.md, and the task acceptance criteria.\\n- Confirm the task owner and required approval in Paperclip.\\n- Use only tools, data, and environments authorized for this company.\\n\\n## Procedure\\n\\n1. Identify classic or block theme architecture, supported versions, theme.json, and design tokens.\\n2. Make presentation changes in the correct template, pattern, or style layer.\\n3. Check responsive behavior, editor/front-end parity, accessibility, and performance.\\n4. Capture visual and automated evidence for relevant templates and states.\\n\\n## Expected result\\n\\nA focused theme change with responsive, accessible, editor, and visual evidence.\\n\\n## Stop and escalate\\n\\nRoute persistent data, business logic, and functional integrations to a plugin or application layer.\\n\\n## References\\n\\n- https://developer.wordpress.org/themes/\\n- https://developer.wordpress.org/themes/global-settings-and-styles/\\n- https://github.com/WordPress/agent-skills\\n\"},{\"slug\":\"run-playbook\",\"title\":\"Run a playbook\",\"description\":\"Use when a Paperclip task carries a playbook, when you are asked to start one, or when your assigned task is a step of a playbook run (a child task created from a flow). Do not use for ordinary tasks that no playbook covers.\",\"markdown\":\"---\\nname: run-playbook\\ndescription: >\\n  Use when a Paperclip task carries a playbook, when you are asked to start one, or when your assigned task is a step of a playbook run (a child task created from a flow). Do not use for ordinary tasks that no playbook covers.\\n---\\n\\n# Run a playbook\\n\\nThis is an original, markdown-only Paperclip skill. It guides work; it does not grant access, make approvals, or replace Paperclip's own task status. Paperclip has no native playbook object: this skill builds the flow out of native tasks, blockers, task documents and execution policies.\\n\\n## Two kinds of playbook\\n\\n- **Checklist** \u2014 `PLAYBOOKS/NN-*.md` in your role folder. Ordered steps for one agent inside one task.\\n- **Flow** \u2014 `PLAYBOOKS/flows/*.yaml` in the folder of the role that owns it. Steps belong to different roles; each `task` step becomes its own Paperclip task, chained with blockers.\\n\\nIf no playbook fits, use the default delivery checklist below.\\n\\n## Run a checklist (one agent, one task)\\n\\n1. Keep the run register in the task document with key `playbook` (format: `templates/PLAYBOOK-REGISTER.md`, shown in the task as plain Markdown). If the document already exists, read it and resume; never start a second run.\\n2. Fill the header: task, one owner, approved outcome and acceptance checks, assumptions, escalation owner, Owner approval status. Copy the steps in order; step 1 is IN_PROGRESS, the rest PENDING.\\n3. Work one step at a time. A step becomes PASS only with evidence on its line (link, artifact, task comment, check output). Then activate only the next step.\\n4. When blocked, mark the step BLOCKED with the reason and who must act, leave later steps PENDING, and put the Paperclip task itself in a waiting state: `blocked` with `blockedByIssueIds`, or a pending interaction with `in_review` for a human decision. Text in the register alone does not stop or wake anyone. Then stop.\\n5. Update the document with the revision-safe procedure of the Paperclip skill (`PUT /api/issues/{issueId}/documents/playbook`, send `baseRevisionId` on updates, reconcile on `409`).\\n6. If you can run scripts, `node validate-run.mjs <register-file>` checks the register (0 valid, 2 valid but halted, 1 invalid). If you cannot run it, check the rules by hand: one IN_PROGRESS step, earlier steps PASS, later steps PENDING, evidence on every PASS.\\n7. When every step is PASS, post an evidence summary and set the task `done`. If the task has an execution policy, `done` moves it to review or approval: that is expected, not an error.\\n\\n## Run a flow (owner role)\\n\\nOnly the agent whose role is the flow's `owner_role` starts it, and only for a task the Owner has approved.\\n\\n1. Read the flow file. Confirm every item in `inputs` from the task text; if one is missing, ask the Owner in the task and stop.\\n2. Resolve each `role` to an active agent with the team briefing tool (`get-team-briefing`) or the company agent list. If a role has no active agent, mark the run BLOCKED and ask the Owner; never substitute another role silently.\\n3. Write the register in the parent task's `playbook` document, listing every step with its owner.\\n4. Create the steps of the current phase. For each `mode: task` step create a child task: `parentId` = the parent task, the assignee, a title, a description with `done_when`, the evidence required and a link to the parent register, and `blockedByIssueIds` = the child tasks of its `depends_on` steps (status `blocked` if it has blockers, otherwise `todo`). Create in dependency order. For a step with `review`, set the task's `executionPolicy` with a `review` stage whose participant is that reviewer; if the API refuses it for your role, ask the Owner to set it in the task. `mode: checklist` steps stay as lines in the parent register, handled by you.\\n5. Slots (`slots:`) name a role chosen by an earlier step. Create the steps that use a slot only after the choosing step is done: Paperclip wakes you when all current children are terminal, then you create the next phase.\\n6. Paperclip wakes each assignee when its blockers are done and wakes you when all children are done. On each wake, copy the child result into the register as PASS with evidence (or BLOCKED), then continue.\\n7. Close out: check every acceptance check against the evidence, post the summary, and set the parent `done`.\\n\\n## With the Playbook Runner plugin\\n\\nIf the tools `playbook-start-flow`, `playbook-complete-step`, `playbook-review-verdict` and `playbook-status` are available, use them instead of creating tasks by hand. As the owner, pass the flow file's text to `playbook-start-flow`: roles are matched to agents by name or title, and you only pass `assignees` (role \u2192 agent id) for the ones it reports as not found. A step with `approval: owner` needs `ownerApproval` (the reference to the Owner's approval, obtained through the CEO) when you close it; close your checklist steps with `playbook-complete-step` (this also supplies the implementer or channel roles you chose). As a reviewer, give your verdict with `playbook-review-verdict`, never by just setting the review task done. The plugin counts the review rounds and opens the escalation task itself. If you hold an escalation task: when you resolved it, set that task done (a new review cycle starts); when your one attempt failed, call `playbook-escalate` with what you tried, and the case goes to the next level (sector head \u2192 CEO \u2192 Owner).\\n\\n## You were assigned a step of a flow\\n\\nRead your task description and the parent register. Do the work inside the stated scope, record the evidence in a task comment, then set the task `done`. A reviewer may follow because of the task's execution policy; if they request changes, fix what they listed and resubmit. If you cannot finish for a reason outside your control, set the task `blocked` and say what is needed and from whom.\\n\\n## Default delivery checklist\\n\\n1. Confirm the assigned task, scope, acceptance checks, owner, dependencies and latest status.\\n2. Inspect the relevant repository, source material, account evidence or existing deliverable; record material unknowns.\\n3. Write the smallest complete plan with assumptions, risks, ordered actions and the evidence you will provide.\\n4. Do the role work in scope and preserve established sources of truth.\\n5. Check each acceptance item against evidence; list gaps, unavailable checks and blockers.\\n6. Attach evidence and hand off in Paperclip; update only your own task.\\n\\n## What is and is not enforced\\n\\n- Enforced by Paperclip: a blocked task does not start until its blockers are done; the parent is woken when its children finish; an execution policy turns `done` into review/approval.\\n- Not enforced: the register is advisory text, and the assignee still sets `done`. Use a review stage wherever evidence must be checked by someone else.\\n\\n## Review loop and escalation\\n\\nEach sector resolves its own work. The Owner assigns to the CEO, the CEO to the sector head (CTO, marketing director, COO, sales lead), the sector head to the team. Escalation moves up one level at a time:\\n\\n1. **Team.** A reviewer in the same sector (for development, QA reviews the implementer) who finds defects uses *request changes* with a concrete list of what fails and how it was seen. The task returns to its producer, who fixes and resubmits. Keep a round counter in the task's `playbook` document or parent register (`round N of 3`); do not rely on Paperclip to count.\\n2. **Sector head.** After the third rejected round, the reviewer stops the loop, wakes the sector head with the defect list and the three rounds' history. The head gets one resolution attempt: change approach, reassign, reduce scope or rewrite the plan, then restarts the loop with the counter reset to 1.\\n3. **CEO.** If the head cannot unblock it, the head hands the CEO what was tried at each level. The CEO gets one attempt.\\n4. **Owner.** Only if the CEO also cannot unblock it, the CEO reports a block to the Owner: what was asked, what each level tried, what decision or resource is missing.\\n\\nA step with `via: ceo` belongs to another sector: do not assign it across sectors yourself. Create it as a task for the CEO, who routes it to the right sector head and reports back. Steps in a flow that are independent of each other run in parallel; steps that depend on another stay chained with blockers. The level order is advisory text, not enforced by Paperclip: say clearly in the task comment at each hand-up who is now responsible.\\n\\n## Stop and escalate to the Owner immediately\\n\\nSpending, publication, hiring, permission changes, production access, legal or safety exposure and irreversible decisions go to the human Owner (through the CEO) without waiting for the loop above. A flow never grants a tool permission or an approval that is not recorded in Paperclip.\\n\\n## References\\n\\n- https://docs.paperclip.ing/guides/power/execution-policy/\\n- https://docs.paperclip.ing/guides/projects-workflow/routines/\\n\"}]}", "import type { PaperclipPluginManifestV1 } from \"@paperclipai/plugin-sdk\";\nimport skill from \"./generated/skill.json\" with { type: \"json\" };\n\nexport const PLUGIN_ID = \"paperclipai.playbook-runner\";\n\nconst manifest: PaperclipPluginManifestV1 = {\n  id: PLUGIN_ID,\n  apiVersion: 1,\n  version: \"0.3.4\",\n  displayName: \"Agents & Workflows\",\n  description: \"Runs agent-static flows: creates the child tasks of each phase, chains review tasks, counts review rounds, and escalates a loop that does not converge to the sector head.\",\n  author: \"Local development plugin\",\n  categories: [\"automation\", \"ui\"],\n  capabilities: [\n    \"issues.read\",\n    \"agents.read\",\n    \"agent.sessions.create\",\n    \"agent.sessions.send\",\n    \"agent.sessions.close\",\n    \"http.outbound\",\n    \"issues.create\",\n    \"issues.update\",\n    \"issue.relations.write\",\n    \"issue.comments.create\",\n    \"issue.documents.read\",\n    \"issue.documents.write\",\n    \"plugin.state.read\",\n    \"plugin.state.write\",\n    \"events.subscribe\",\n    \"agent.tools.register\",\n    \"skills.managed\",\n    \"ui.sidebar.register\",\n    \"ui.page.register\",\n  ],\n  entrypoints: { worker: \"./dist/worker.js\", ui: \"./dist/ui\" },\n  ui: { slots: [\n    { type: \"sidebar\", id: \"playbook-sidebar\", displayName: \"Agents & Workflows\", exportName: \"PlaybookSidebar\", order: 99 },\n    { type: \"page\", id: \"playbook-page\", displayName: \"Agents & Workflows\", exportName: \"PlaybookPage\", routePath: \"agents-workflows\" },\n  ] },\n  skills: skill.skills.map((s) => ({ skillKey: s.slug, displayName: s.title, slug: s.slug, description: String(s.description).replace(/\\s+/g, \" \").trim().slice(0, 300), markdown: s.markdown })),\n  tools: [\n    {\n      name: \"playbook-start-flow\",\n      displayName: \"Start a playbook flow\",\n      description: \"Owner of a flow only. Instantiates a flow file (PLAYBOOKS/flows/*.yaml) on the parent task: creates the child tasks of the first phase, the review tasks and the run register document.\",\n      parametersSchema: {\n        type: \"object\",\n        properties: {\n          parentIssueId: { type: \"string\" },\n          flowKey: { type: \"string\" },\n          flowYaml: { type: \"string\" },\n          assignees: { type: \"object\", additionalProperties: { type: \"string\" } },\n          slotChoices: { type: \"object\", additionalProperties: { type: \"array\", items: { type: \"string\" } } },\n          includeOptional: { type: \"array\", items: { type: \"string\" } },\n          outcome: { type: \"string\" },\n          approval: { type: \"string\" },\n        },\n        required: [\"parentIssueId\"],\n      },\n    },\n    {\n      name: \"playbook-complete-step\",\n      displayName: \"Complete a checklist step of a flow\",\n      description: \"Owner of a flow only. Marks one of your own checklist steps done with evidence and creates whatever becomes ready. Also supplies slot choices or missing assignees.\",\n      parametersSchema: {\n        type: \"object\",\n        properties: {\n          parentIssueId: { type: \"string\" },\n          stepId: { type: \"string\" },\n          evidence: { type: \"string\" },\n          ownerApproval: { type: \"string\" },\n          slotChoices: { type: \"object\", additionalProperties: { type: \"array\", items: { type: \"string\" } } },\n          assignees: { type: \"object\", additionalProperties: { type: \"string\" } },\n        },\n        required: [\"parentIssueId\"],\n      },\n    },\n    {\n      name: \"playbook-review-verdict\",\n      displayName: \"Give the verdict on a review task\",\n      description: \"Reviewer only. approve closes the step; changes sends the work back with your defect list, and after the maximum rounds the step is escalated to the sector head.\",\n      parametersSchema: {\n        type: \"object\",\n        properties: {\n          reviewIssueId: { type: \"string\" },\n          verdict: { type: \"string\", enum: [\"approve\", \"changes\"] },\n          defects: { type: \"string\" },\n        },\n        required: [\"reviewIssueId\", \"verdict\"],\n      },\n    },\n    {\n      name: \"playbook-escalate\",\n      displayName: \"Hand an escalation up one level\",\n      description: \"Holder of an escalation task only, after your one resolution attempt failed. Hands the case to the next level (sector head -> CEO -> Owner) with what you tried.\",\n      parametersSchema: { type: \"object\", properties: { escalationIssueId: { type: \"string\" }, tried: { type: \"string\" } }, required: [\"escalationIssueId\", \"tried\"] },\n    },\n    {\n      name: \"playbook-status\",\n      displayName: \"Show the register of a running flow\",\n      description: \"Returns the run register and per-step state of the flow running on a parent task.\",\n      parametersSchema: { type: \"object\", properties: { parentIssueId: { type: \"string\" } }, required: [\"parentIssueId\"] },\n    },\n  ],\n};\n\nexport default manifest;\n"],
   "mappings": ";AAAA,sBAAC,QAAS,CAAC,EAAC,MAAO,gCAA+B,OAAQ,gCAA+B,aAAc,0NAAyN,UAAW,gkDAA+jD,GAAE,EAAC,MAAO,+BAA8B,OAAQ,+BAA8B,aAAc,6LAA4L,UAAW,8lDAA6lD,GAAE,EAAC,MAAO,yCAAwC,OAAQ,yCAAwC,aAAc,qNAAoN,UAAW,6nDAA4nD,GAAE,EAAC,MAAO,sCAAqC,OAAQ,sCAAqC,aAAc,4HAA2H,UAAW,qhEAAohE,GAAE,EAAC,MAAO,kCAAiC,OAAQ,kCAAiC,aAAc,8MAA6M,UAAW,uhDAAshD,GAAE,EAAC,MAAO,kBAAiB,OAAQ,6BAA4B,aAAc,yLAAwL,UAAW,m+CAAk+C,GAAE,EAAC,MAAO,wBAAuB,OAAQ,wBAAuB,aAAc,gOAA+N,UAAW,mhDAAkhD,GAAE,EAAC,MAAO,kCAAiC,OAAQ,kCAAiC,aAAc,2LAA0L,UAAW,qhDAAohD,GAAE,EAAC,MAAO,wCAAuC,OAAQ,wCAAuC,aAAc,uMAAsM,UAAW,shDAAqhD,GAAE,EAAC,MAAO,6BAA4B,OAAQ,6BAA4B,aAAc,6LAA4L,UAAW,2+CAA0+C,GAAE,EAAC,MAAO,8BAA6B,OAAQ,8BAA6B,aAAc,oLAAmL,UAAW,87CAA67C,GAAE,EAAC,MAAO,gCAA+B,OAAQ,gCAA+B,aAAc,+KAA8K,UAAW,shDAAqhD,GAAE,EAAC,MAAO,sBAAqB,OAAQ,sBAAqB,aAAc,wJAAuJ,UAAW,88CAA68C,GAAE,EAAC,MAAO,6BAA4B,OAAQ,qCAAoC,aAAc,kMAAiM,UAAW,g9CAA+8C,GAAE,EAAC,MAAO,6BAA4B,OAAQ,6BAA4B,aAAc,wLAAuL,UAAW,k9CAAi9C,GAAE,EAAC,MAAO,yBAAwB,OAAQ,sCAAqC,aAAc,oMAAmM,UAAW,m/CAAk/C,GAAE,EAAC,MAAO,+BAA8B,OAAQ,uCAAsC,aAAc,mMAAkM,UAAW,qkDAAokD,GAAE,EAAC,MAAO,sCAAqC,OAAQ,sCAAqC,aAAc,4KAA2K,UAAW,u9CAAs9C,GAAE,EAAC,MAAO,gCAA+B,OAAQ,gCAA+B,aAAc,2KAA0K,UAAW,2gDAA0gD,GAAE,EAAC,MAAO,0CAAyC,OAAQ,0CAAyC,aAAc,4NAA2N,UAAW,u8CAAs8C,GAAE,EAAC,MAAO,iCAAgC,OAAQ,iCAAgC,aAAc,oMAAmM,UAAW,+4CAA84C,GAAE,EAAC,MAAO,gCAA+B,OAAQ,gCAA+B,aAAc,+KAA8K,UAAW,m5CAAk5C,GAAE,EAAC,MAAO,6BAA4B,OAAQ,6BAA4B,aAAc,+LAA8L,UAAW,g3CAA+2C,GAAE,EAAC,MAAO,4BAA2B,OAAQ,4BAA2B,aAAc,mLAAkL,UAAW,w4CAAu4C,GAAE,EAAC,MAAO,gCAA+B,OAAQ,gCAA+B,aAAc,0KAAyK,UAAW,i8CAAg8C,GAAE,EAAC,MAAO,iCAAgC,OAAQ,iCAAgC,aAAc,mLAAkL,UAAW,+hDAA8hD,GAAE,EAAC,MAAO,sBAAqB,OAAQ,uBAAsB,aAAc,mMAAkM,UAAW,sjDAAqjD,GAAE,EAAC,MAAO,0BAAyB,OAAQ,0BAAyB,aAAc,0MAAyM,UAAW,wjDAAujD,GAAE,EAAC,MAAO,8BAA6B,OAAQ,8BAA6B,aAAc,4KAA2K,UAAW,49CAA29C,GAAE,EAAC,MAAO,gCAA+B,OAAQ,gCAA+B,aAAc,uKAAsK,UAAW,4+CAA2+C,GAAE,EAAC,MAAO,+BAA8B,OAAQ,+BAA8B,aAAc,gMAA+L,UAAW,2/CAA0/C,GAAE,EAAC,MAAO,gBAAe,OAAQ,kBAAiB,aAAc,oOAAmO,UAAW,k1RAAwzR,CAAC,EAAC;;;ACG5ghE,IAAM,YAAY;AAEzB,IAAM,WAAsC;AAAA,EAC1C,IAAI;AAAA,EACJ,YAAY;AAAA,EACZ,SAAS;AAAA,EACT,aAAa;AAAA,EACb,aAAa;AAAA,EACb,QAAQ;AAAA,EACR,YAAY,CAAC,cAAc,IAAI;AAAA,EAC/B,cAAc;AAAA,IACZ;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,EACF;AAAA,EACA,aAAa,EAAE,QAAQ,oBAAoB,IAAI,YAAY;AAAA,EAC3D,IAAI,EAAE,OAAO;AAAA,IACX,EAAE,MAAM,WAAW,IAAI,oBAAoB,aAAa,sBAAsB,YAAY,mBAAmB,OAAO,GAAG;AAAA,IACvH,EAAE,MAAM,QAAQ,IAAI,iBAAiB,aAAa,sBAAsB,YAAY,gBAAgB,WAAW,mBAAmB;AAAA,EACpI,EAAE;AAAA,EACF,QAAQ,cAAM,OAAO,IAAI,CAAC,OAAO,EAAE,UAAU,EAAE,MAAM,aAAa,EAAE,OAAO,MAAM,EAAE,MAAM,aAAa,OAAO,EAAE,WAAW,EAAE,QAAQ,QAAQ,GAAG,EAAE,KAAK,EAAE,MAAM,GAAG,GAAG,GAAG,UAAU,EAAE,SAAS,EAAE;AAAA,EAC9L,OAAO;AAAA,IACL;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,aAAa;AAAA,MACb,kBAAkB;AAAA,QAChB,MAAM;AAAA,QACN,YAAY;AAAA,UACV,eAAe,EAAE,MAAM,SAAS;AAAA,UAChC,SAAS,EAAE,MAAM,SAAS;AAAA,UAC1B,UAAU,EAAE,MAAM,SAAS;AAAA,UAC3B,WAAW,EAAE,MAAM,UAAU,sBAAsB,EAAE,MAAM,SAAS,EAAE;AAAA,UACtE,aAAa,EAAE,MAAM,UAAU,sBAAsB,EAAE,MAAM,SAAS,OAAO,EAAE,MAAM,SAAS,EAAE,EAAE;AAAA,UAClG,iBAAiB,EAAE,MAAM,SAAS,OAAO,EAAE,MAAM,SAAS,EAAE;AAAA,UAC5D,SAAS,EAAE,MAAM,SAAS;AAAA,UAC1B,UAAU,EAAE,MAAM,SAAS;AAAA,QAC7B;AAAA,QACA,UAAU,CAAC,eAAe;AAAA,MAC5B;AAAA,IACF;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,aAAa;AAAA,MACb,kBAAkB;AAAA,QAChB,MAAM;AAAA,QACN,YAAY;AAAA,UACV,eAAe,EAAE,MAAM,SAAS;AAAA,UAChC,QAAQ,EAAE,MAAM,SAAS;AAAA,UACzB,UAAU,EAAE,MAAM,SAAS;AAAA,UAC3B,eAAe,EAAE,MAAM,SAAS;AAAA,UAChC,aAAa,EAAE,MAAM,UAAU,sBAAsB,EAAE,MAAM,SAAS,OAAO,EAAE,MAAM,SAAS,EAAE,EAAE;AAAA,UAClG,WAAW,EAAE,MAAM,UAAU,sBAAsB,EAAE,MAAM,SAAS,EAAE;AAAA,QACxE;AAAA,QACA,UAAU,CAAC,eAAe;AAAA,MAC5B;AAAA,IACF;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,aAAa;AAAA,MACb,kBAAkB;AAAA,QAChB,MAAM;AAAA,QACN,YAAY;AAAA,UACV,eAAe,EAAE,MAAM,SAAS;AAAA,UAChC,SAAS,EAAE,MAAM,UAAU,MAAM,CAAC,WAAW,SAAS,EAAE;AAAA,UACxD,SAAS,EAAE,MAAM,SAAS;AAAA,QAC5B;AAAA,QACA,UAAU,CAAC,iBAAiB,SAAS;AAAA,MACvC;AAAA,IACF;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,aAAa;AAAA,MACb,kBAAkB,EAAE,MAAM,UAAU,YAAY,EAAE,mBAAmB,EAAE,MAAM,SAAS,GAAG,OAAO,EAAE,MAAM,SAAS,EAAE,GAAG,UAAU,CAAC,qBAAqB,OAAO,EAAE;AAAA,IACjK;AAAA,IACA;AAAA,MACE,MAAM;AAAA,MACN,aAAa;AAAA,MACb,aAAa;AAAA,MACb,kBAAkB,EAAE,MAAM,UAAU,YAAY,EAAE,eAAe,EAAE,MAAM,SAAS,EAAE,GAAG,UAAU,CAAC,eAAe,EAAE;AAAA,IACrH;AAAA,EACF;AACF;AAEA,IAAO,mBAAQ;",
   "names": []
 }