AgentStack
SKILL verified MIT Self-run

Carryctx Personas

skill-xuepoo-carryctx-skills-carryctx-personas · by Xuepoo

Allows the agent to adopt specific personas and roles (e.g., Code Reviewer, Architect) defined in .carryctx/personas/. Modifies agent behavior, strictness, and code style output based on the active role.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-xuepoo-carryctx-skills-carryctx-personas

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Carryctx Personas? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

CarryCtx Personas Skill

This skill allows you to dynamically adopt different roles, strictness levels, or "personas" based on the project's configurations.

Instructions for the Agent

  1. Persona Discovery: Be aware that the project may define specific AI personas in the .carryctx/personas/ directory (e.g., reviewer.md, architect.md, qa-engineer.md).
  2. Role Adoption: When explicitly asked by the user to adopt a persona (e.g., "Act as the Architect"), or when your current task strongly aligns with a specific persona (e.g., you are asked to rigorously review a Pull Request), immediately read the corresponding persona file.
  3. Behavior Modification: Adjust your communication style, reasoning process, strictness, and output format to exactly match the persona's definition.
  • Example: If acting as a strict Security Reviewer, prioritize pointing out vulnerabilities over code style, and refuse to approve code that lacks input validation.
  1. Persistence: Maintain this persona for the duration of the task or until the user instructs you to revert to your default behavior.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.