all publishers

weorbitant

@weorbitant source repo

77 published skills

  1. ▌
    Adr 2 · weorbitant bundle
    Use when creating, updating, or compacting Architecture Decision Records (ADRs). Use when user says "adr", "crear ADR", "create ADR", "actualizar ADR", "update ADR", "compactar ADR", "compact ADR", "registrar decision", "record decision", "decision record".
    9 repo stars
  2. ▌
    DB Query 2 · weorbitant bundle
    Use when needing to query a PostgreSQL database in DEV or PROD, check if records exist, count rows, inspect data, or run read-only SQL queries from within the cluster. Use when user says "consulta la BD", "query", "busca en la tabla", "check database", "db query", or "existe este registro".
    9 repo stars
  3. ▌
    Notify Team 2 · weorbitant bundle
    Use when sending any communication to the team — incidents, announcements, questions, status updates, or review requests. Use when user says "notifica al equipo", "avisa al equipo", "crea un mensaje", "anuncia", "pregunta al equipo", "draft a message", or wants to communicate anything to the team via Slack.
    9 repo stars
  4. ▌
    Analyze Docs 2 · weorbitant
    Use when searching for documentation about a concept, entity, or business term in Confluence and Notion. Extracts definitions and rules without interpretation. Use when user says "busca documentación", "qué dice confluence", "analyze docs", "busca en notion", "hay documentación sobre", or "qué sabemos de".
    9 repo stars
  5. ▌
    Sprint Review 2 · weorbitant bundle
    Use when evaluating a sprint before starting it. Detects duplicates, poorly defined tickets, missing acceptance criteria, estimation gaps, vague language, dependency risks, and balance issues. Use when user says "revisa sprint", "sprint review", "analiza sprint", "sprint health", "evalúa sprint", or provides a list of ticket keys for pre-sprint review.
    9 repo stars
  6. ▌
    Analyze Design 2 · weorbitant
    Use when analyzing Figma designs to extract data fields, UI states, and actions without assumptions. Uses Figma MCP with Playwright fallback. Use when user says "analiza diseño", "revisa el figma", "qué campos tiene el diseño", "analyze design", or shares a Figma URL for review.
    9 repo stars
  7. ▌
    Ticket Analysis 2 · weorbitant bundle
    Use when doing comprehensive ticket analysis before implementation. Analyzes Jira ticket, Figma designs, Confluence/Notion docs, and codebase to produce a data map where every field is questioned and scope is explicitly defined. Use when user says "analiza ticket", "ticket analysis", "prepara ticket", "revisar ticket completo", or "qué falta en este ticket".
    9 repo stars
  8. ▌
    Analyze Data Model 2 · weorbitant
    Use when interrogating the codebase to understand an entity, field, or business concept. Traces data origin, mutations, validations, and relationships without assumptions. Use when user says "analiza entidad", "de dónde viene este dato", "analyze data model", "qué campos tiene", "quién genera este campo", or "explica esta entidad".
    9 repo stars
  9. ▌
    Creating Skills 2 · weorbitant bundle
    Use when creating new skills, editing existing skills, or reviewing skill quality. Use when user mentions building, writing, or improving a SKILL.md file or skill folder. Guides skill authoring following Anthropic's official best practices.
    9 repo stars
  10. ▌
    New Learning · weorbitant
    Use when the user wants to find what to learn next, explore learning topics, get project ideas for a skill gap, or add a learning idea to their backlog. Triggers on: "what should I learn", "suggest learning projects", "I want to learn X", "add to my learning backlog", or "find me resources on X".
    9 repo stars
  11. ▌
    Learning Status · weorbitant
    Use when the user wants a fast status check on their learning without a full report. Triggers on: "learning status", "where am I", "what's my learning state", "how's my learning going", or "check my progress".
    9 repo stars
  12. ▌
    Learning Insights · weorbitant
    Internal-only skill — never called directly by users. Provides the Learning Intelligence Layer. Two modes: "build context" (called by /learn at session start) reads learning history and produces a learner context; "update insights" (called by /end-learn after session close) updates the persistent insights.md summary.
    9 repo stars
  13. ▌
    Blog Post Review · weorbitant bundle
    Editorial review skill for Orbitant engineering blog posts. Activates when reviewing, editing, or providing feedback on blog articles. Produces structured reviews covering SEO, content quality, tone, and actionable improvements. Responds in the same language as the article being reviewed.
    9 repo stars
  14. ▌
    Learn · weorbitant
    Use when the user wants to sit down and learn, continue a lesson, practice a skill, or work through a learning project. Triggers on: "let's learn", "continue my lesson", "start learning", "practice", "I have time to learn", or "pick up where I left off".
    9 repo stars
  15. ▌
    Debrief · weorbitant
    Use at the end of a Claude Code session to capture project-specific friction as proposed CLAUDE.md edits. Triggered by /debrief (no args) to scan the full session, or /debrief <hint> to focus on a specific area (e.g., /debrief the API naming convention thing). Returning "session looks clean" with no proposals is a first-class outcome, not a fallback. Triggers on: "/debrief", "debrief the session", "wrap up this session", "what did we learn", "any rules to capture", "should we update CLAUDE.md".
    9 repo stars
  16. ▌
    End Learn · weorbitant
    Use when the user is done learning for the day, wants to save progress, or wants to wrap up a lesson. Also triggered by /learn when postponing or abandoning. Updates the learning intelligence layer (insights.md) after each session. Triggers on: "end session", "done learning", "save progress", "wrap up", "end-learn", "I'm done for today".
    9 repo stars
  17. ▌
    Init Learning · weorbitant
    Use when the user wants to set up or update their learning profile, configure learning preferences, update their role or gaps, add feedback from reviews or 1:1s, or when any other learning skill detects no profile exists. Triggers on: "set up learning", "update my learning profile", "init learning", or pasting performance feedback.
    9 repo stars
  18. ▌
    Learning Report · weorbitant
    Use when the user wants to review what they've learned, see progress on their gaps, get a summary of recent learning sessions, or wants article ideas based on learnings. Triggers on: "learning report", "what have I learned", "progress report", "summarize my learning", or "learning summary for the last month".
    9 repo stars
  19. ▌
    Infra Logs · weorbitant
    Use when checking pod logs, searching for errors, viewing recent log output, or debugging runtime issues in DEV or PROD. Use when user says "logs de", "ver logs", "qué errores hay", "check logs", "show errors", or mentions log analysis of a service.
    9 repo stars
  20. ▌
    Infra Pods · weorbitant
    Use when checking pod status, listing running services, investigating crashloops, viewing pod events, or checking resource usage. Use when user says "pods", "qué está corriendo", "pod status", "check pods", "restart", "crashloop", or "pod events".
    9 repo stars
  21. ▌
    Infra Deploy · weorbitant bundle
    Use when user asks to deploy to production, check what's deployed, find a docker image tag for a PR, or trigger a production deployment. Use when user mentions "deploy", "prod", "production", "release", or "ship".
    9 repo stars
  22. ▌
    Creating Skills · weorbitant bundle
    Use when creating new skills, editing existing skills, or reviewing skill quality. Use when user mentions building, writing, or improving a SKILL.md file or skill folder. Guides skill authoring following Anthropic's official best practices.
    9 repo stars
  23. ▌
    Jira Create Bug · weorbitant
    Use when creating a bug report in Jira, reporting an issue found during development or operations, or filing a ticket for a production problem. Use when user says "crea un bug", "reporta bug", "create bug", "file a bug", "abre un ticket", or "report issue".
    9 repo stars
  24. ▌
    Infra Migrations · weorbitant bundle
    Use when user asks to run database migrations, create tables, apply schema changes, or mentions "migration" in the context of DEV or PROD environments. Use when user mentions "migrate", "migration:up", "create table", or "schema changes" for remote environments.
    9 repo stars
  25. ▌
    Infra Portforward · weorbitant bundle
    Use when needing to port-forward to any Kubernetes service (RabbitMQ, PostgreSQL, internal APIs). Use when user says "port-forward", "portforward", "connect to", "forward port", or needs local access to a cluster service in DEV or PROD.
    9 repo stars
  26. ▌
    Jira Clarify Ticket · weorbitant bundle
    Use when analyzing a Jira ticket for ambiguities, missing information, or unclear acceptance criteria. Use when user says "clarify ticket", "review ticket", "analyze ticket", or passes a Jira ticket key like DEVPT-XX. Reads the ticket from Jira, detects vague content, and generates concrete questions.
    9 repo stars
  27. ▌
    Rabbitmq Triage Dlq · weorbitant bundle
    Use when investigating why messages are failing in a RabbitMQ Dead Letter Queue (DLQ), diagnosing root causes of message rejections, or analyzing DLQ message patterns. Use when user says "triage DLQ", "why are messages failing", "analyze DLQ", "diagnose DLQ", "analiza esta cola", or wants to understand message failures before deciding whether to reprocess or purge.
    9 repo stars
  28. ▌
    Rabbitmq List Queues · weorbitant
    Use when checking RabbitMQ queue status, listing queues with messages, checking DLQ counts, or monitoring consumer health. Use when user says "list queues", "lista colas", "queue status", "cuántos mensajes", "check queues", or "DLQ status".
    9 repo stars
  29. ▌
    Rabbitmq Reprocess Dlq · weorbitant
    Use when needing to reprocess messages from a RabbitMQ Dead Letter Queue (DLQ), move messages between queues using shovel, republish with clean headers, or purge unprocessable messages. Use when user mentions "reprocess", "reprocesar", "shovel", "purge DLQ", or "move messages from DLQ".
    9 repo stars
  30. ▌
    Adr · weorbitant bundle
    Use when creating, updating, or compacting Architecture Decision Records. Use when user says 'adr', 'create ADR', 'record decision', 'registrar decisión', 'decision record', or needs to document a technical decision.
    9 repo stars
  31. ▌
    Deploy · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  32. ▌
    DB Query · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  33. ▌
    Configure · weorbitant bundle
    UI Rules — MANDATORY
    9 repo stars
  34. ▌
    Create Bug · weorbitant bundle
    Use when creating a well-structured bug report with root cause analysis. Use when user says 'create bug', 'report bug', 'log bug', 'new bug', or describes a defect.
    9 repo stars
  35. ▌
    DB Migrate · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  36. ▌
    Notify Team · weorbitant bundle
    Use when sending communication to the team. Use when user says 'notify team', 'notifica al equipo', 'send message', 'draft a message', 'enviar mensaje', or needs to communicate with the team.
    9 repo stars
  37. ▌
    Analyze Docs · weorbitant bundle
    Use when searching documentation about a concept across platforms. Use when user says 'search docs', 'buscar documentación', 'analyze docs', 'find documentation', or needs to understand existing documentation about a topic.
    9 repo stars
  38. ▌
    Port Forward · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  39. ▌
    Queue Status · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  40. ▌
    Queue Triage · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  41. ▌
    Service Logs · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  42. ▌
    Sprint Review · weorbitant bundle
    Use when evaluating a sprint before starting it. Use when user says 'sprint review', 'review sprint', 'evaluar sprint', 'sprint planning review', or mentions checking sprint readiness.
    9 repo stars
  43. ▌
    Deploy Status · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  44. ▌
    Analyze Design · weorbitant bundle
    Use when extracting data fields, UI states, actions, and flows from a design. Use when user says 'analyze design', 'analizar diseño', 'review design', 'extract from figma', or shares a design URL.
    9 repo stars
  45. ▌
    Clarify Ticket · weorbitant bundle
    Use when analyzing a ticket for ambiguities, missing information, or unclear acceptance criteria. Use when user says 'clarify ticket', 'review ticket', 'analyze ticket', or passes a ticket key.
    9 repo stars
  46. ▌
    Service Status · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  47. ▌
    Ticket Analysis · weorbitant bundle
    Use when performing a comprehensive ticket analysis across design, documentation, data model, and technical feasibility. Use when user says 'analyze ticket', 'ticket analysis', 'análisis de ticket', or needs deep understanding before implementation.
    9 repo stars
  48. ▌
    Queue Reprocess · weorbitant bundle
    Step 0 — Load configuration
    9 repo stars
  49. ▌
    Workflow Deploy · weorbitant bundle
    Overview
    9 repo stars
  50. ▌
    Board To Stories · weorbitant bundle
    Use when extracting user stories from a visual board. Use when user says 'extract stories', 'genera user stories', 'procesa scope', 'board to stories', or shares a board URL.
    9 repo stars
  51. ▌
    Analyze Data Model · weorbitant
    Use when interrogating the codebase to understand an entity, its fields, relationships, and data flows. Use when user says 'analyze data model', 'analizar modelo', 'understand entity', 'check schema', or asks about a specific entity or database field.
    9 repo stars
  52. ▌
    Analyze Feasibility · weorbitant
    Use when evaluating whether a technical approach is feasible against the current codebase. Use when user says 'analyze feasibility', 'is this feasible', 'evaluar factibilidad', 'technical analysis', or asks whether an approach will work.
    9 repo stars
  53. ▌
    Orbitant Release Notes · weorbitant
    Drafts structured, publication-ready release notes from git history. Activates when: creating releases, documenting version changes, drafting changelogs, or preparing release announcements. Use even when user just says "generate changelog", "what changed since last release", "help me write release notes", "prepare a release", or "I bumped the version". Also triggers after version bumps in plugin.json.
    9 repo stars
  54. ▌
    Skill Reviewer · weorbitant
    Reviews SKILL.md files for quality and compliance with orbitant-os conventions. Use when: reviewing a skill, checking skill quality, validating skill format, or when asked to "review this skill" or "check if this skill is good". Also activates for CI skill validation requests.
    9 repo stars
  55. ▌
    Orbitant Tone · weorbitant
    Voice and tone reference for Orbitant blog content. Defines what Orbitant writing sounds like, what it values, and what it avoids — with concrete examples. Activate when user asks about Orbitant voice, tone, writing style, brand voice, or editorial guidelines. Also trigger when reviewing blog content for consistency, checking if text "sounds like Orbitant", or when creating/editing marketing content — even if they don't explicitly mention tone or voice.
    9 repo stars
  56. ▌
    Orbitant Learn · weorbitant
    Use when the user wants to sit down and learn, continue a lesson, practice a skill, or work through a learning project. Triggers on: "let's learn", "continue my lesson", "start learning", "practice", "I have time to learn", or "pick up where I left off".
    9 repo stars
  57. ▌
    Orbitant Debrief · weorbitant
    Use at the end of a Claude Code session to capture project-specific friction as proposed CLAUDE.md edits. Triggered by /debrief (no args) to scan the full session, or /debrief <hint> to focus on a specific area (e.g., /debrief the API naming convention thing). Returning "session looks clean" with no proposals is a first-class outcome, not a fallback. Triggers on: "/debrief", "debrief the session", "wrap up this session", "what did we learn", "any rules to capture", "should we update CLAUDE.md".
    9 repo stars
  58. ▌
    Orbitant Newsletter · weorbitant
    Drafts the monthly Orbitant newsletter from Slack links, Knowledge Sharing recaps, blog posts, and meetup updates. Activate when the user mentions "newsletter", "monthly email", "prepare the newsletter", "newsletter de [mes]", "borrador de newsletter", or provides materials for the monthly send (KS recap, Slack links, blog posts). Also triggers when asked to "draft the email for this month" or "prepare the MailerLite send". Curates Slack channel links autonomously, writes all copy in English, and outputs a complete Markdown draft ready for MailerLite layout.
    9 repo stars
  59. ▌
    Orbitant 12 Factor · weorbitant bundle
    Use when checking if a repo follows 12-factor app principles — config stored in env vars (not hardcoded), dependency lockfiles present, CI pipeline separation, structured logging to stdout, or dev/prod environment parity. Activates when someone asks about 12-factor compliance, deployment readiness, or config management practices in a Node.js or Python project. Also trigger when someone notices hardcoded localhost URLs, missing .env.example, or asks "is this deploy-ready?" — even without mentioning 12-factor explicitly.
    9 repo stars
  60. ▌
    Orbitant End Learn · weorbitant
    Use when the user is done learning for the day, wants to save progress, or wants to wrap up a lesson. Also triggered by /learn when postponing or abandoning. Updates the learning intelligence layer (insights.md) after each session. Triggers on: "end session", "done learning", "save progress", "wrap up", "end-learn", "I'm done for today".
    9 repo stars
  61. ▌
    Orbitant Owasp Scan · weorbitant bundle
    Use when scanning a Node.js or Python repo for OWASP Top 10 vulnerabilities — hardcoded secrets, SQL injection patterns, weak cryptography, dangerous functions (eval, exec, shell=True), missing security headers, or dependency lockfile issues. Activates when someone asks about security posture, wants a static security scan, or needs to assess risk before a code review or client engagement.
    9 repo stars
  62. ▌
    Orbitant Git Hygiene · weorbitant bundle
    Use when auditing git practices in a repo — Conventional Commits compliance, branch naming standards, secrets committed to history, direct commits to main, or stale branches. Activates when someone asks "is the git hygiene good here?", wants to check commit discipline, or needs to assess branch/release health before starting work on a project. Also trigger when someone asks "are my commits OK?", "is my branch name right?", or shares a git log — even if they don't explicitly mention "hygiene".
    9 repo stars
  63. ▌
    Orbitant Linkedin Post · weorbitant
    LinkedIn content planner for Orbitant. Takes a published blog post (markdown) and produces a full content plan with multiple LinkedIn pieces ready for scheduling: a standard post with link, a carousel structure proposal, and a multimedia asset recommendation (infographic or diagram). Each piece uses a different angle from the same source material. Output is ready for handoff to n8n or manual scheduling. Activate when user shares a blog post and asks for LinkedIn content, social media copy, a content plan, carousel proposals, or content repurposing for LinkedIn. Also trigger when asked to "turn this into LinkedIn posts", "create social media from this article", or "help me schedule this content" — even if they don't explicitly mention LinkedIn or social media strategy.
    9 repo stars
  64. ▌
    Orbitant AI Readiness · weorbitant bundle
    Use when auditing whether a repo is configured for AI-assisted development — checking .claude/ setup quality, CLAUDE.md completeness, skills/agents presence, hooks, memory, or MCP server configuration. Activates when someone asks "is this repo AI-ready?", "how well is Claude configured here?", or wants to assess AI readiness before starting work on an unfamiliar project. Also trigger when reviewing any .claude/ config, CLAUDE.md quality, or hooks setup — even if the user doesn't explicitly mention "AI readiness".
    9 repo stars
  65. ▌
    Orbitant New Learning · weorbitant
    Use when the user wants to find what to learn next, explore learning topics, get project ideas for a skill gap, or add a learning idea to their backlog. Triggers on: "what should I learn", "suggest learning projects", "I want to learn X", "add to my learning backlog", or "find me resources on X".
    9 repo stars
  66. ▌
    Orbitant Image Creation · weorbitant bundle
    Generates blog post thumbnail images for Orbitant following the brand's visual identity, using Google's Gemini image API (Nano Banana 2). Activates when creating blog images, generating thumbnails, designing featured images for articles, or when someone needs a visual for an Orbitant insight/blog post. Use this skill even if the user just says "I need an image for this article", "create a thumbnail", "generate a hero image", or "make a featured image". Also triggers when the user mentions "Nano Banana 2", "image generation", or asks for a prompt for an AI image tool.
    9 repo stars
  67. ▌
    Orbitant Yt Description · weorbitant
    YouTube video description generator for Orbitant Knowledge Sharing (KS) sessions. Takes a session transcript (.vtt or plain text) and produces a bilingual, SEO-optimised YouTube description — Spanish first, then English — built around a positionable keyword. The description is structured to rank in YouTube and Google search: keyword in the first line, natural repetition in the overview and takeaways, and hashtags chosen for search intent, not just labels. Use this skill whenever someone needs to write or generate a YouTube description for a KS session or any Orbitant video — even if they just say "escribe la descripción del vídeo", "I need the YouTube copy", or "help me upload this session". Also trigger when given a transcript and asked to prepare anything for a video upload.
    9 repo stars
  68. ▌
    Orbitant Init Learning · weorbitant
    Use when the user wants to set up or update their learning profile, configure learning preferences, update their role or gaps, add feedback from reviews or 1:1s, or when any other learning skill detects no profile exists. Triggers on: "set up learning", "update my learning profile", "init learning", or pasting performance feedback.
    9 repo stars
  69. ▌
    Orbitant Goal Alignment · weorbitant
    Scores items against quarterly rocks from rocks.yaml. Activates during triage, task ranking, meeting prep, and scheduling. Flags drift when time allocation mismatches stated priorities.
    9 repo stars
  70. ▌
    Orbitant Voice Drafting · weorbitant
    Writes drafts in the user's voice using voice.md for tone and style. Activates during /triage, /crm, or any "draft an email/message" request. Never sends without confirmation.
    9 repo stars
  71. ▌
    Orbitant Blog Post Create · weorbitant bundle
    Content generation skill for the Orbitant engineering blog. Activates when creating a blog post in Spanish from raw input — a Knowledge Sharing transcript, Slack thread, meeting notes, workshop draft, or bullet outline. Produces a structured, SEO-optimised article that matches Orbitant's narrative, tone, and content cluster strategy. Trigger on: "crear blog post", "redactar artículo", "convierte esto en un post", "blog post para Orbitant", "write a blog post", "turn this into an article". Also trigger when the user shares a long transcript, KS notes, or a Slack discussion about a technical decision — even if they don't explicitly say "blog post". When in doubt, ask if they want this turned into a post.
    9 repo stars
  72. ▌
    Orbitant Blog Post Review · weorbitant
    Editorial review skill for Orbitant engineering blog posts. Activates when reviewing, editing, or providing feedback on blog articles. Produces structured reviews covering SEO, content quality, tone, and actionable improvements. Responds in the same language as the article being reviewed. Use this skill whenever someone asks to review a blog post, wants editorial feedback on a draft, needs SEO analysis for an article, or requests writing improvements for the Orbitant blog — even if they don't explicitly mention "review".
    9 repo stars
  73. ▌
    Orbitant Learning Report · weorbitant
    Use when the user wants to review what they've learned, see progress on their gaps, get a summary of recent learning sessions, or wants article ideas based on learnings. Triggers on: "learning report", "what have I learned", "progress report", "summarize my learning", or "learning summary for the last month".
    9 repo stars
  74. ▌
    Orbitant Learning Status · weorbitant
    Use when the user wants a fast status check on their learning without a full report. Triggers on: "learning status", "where am I", "what's my learning state", "how's my learning going", or "check my progress".
    9 repo stars
  75. ▌
    Orbitant Learning Insights · weorbitant
    Internal-only skill — never called directly by users. Provides the Learning Intelligence Layer. Two modes: "build context" (called by /learn at session start) reads learning history and produces a learner context; "update insights" (called by /end-learn after session close) updates the persistent insights.md summary.
    9 repo stars
  76. ▌
    Orbitant Blog Post Translate · weorbitant
    Translation skill for validated Orbitant blog posts. Takes a Spanish article that has already been reviewed and approved by a human editor, and produces an English version optimised for English-speaking audiences. Keyword selection is not a literal translation but a search-intent-driven choice for the English market. Use this skill only on articles that have completed the full editorial and review process.
    9 repo stars
  77. ▌
    Orbitant Graceful Degradation · weorbitant
    Checks MCP servers and config files before any chief-of-staff command. Ensures no command hard-fails — always proceeds with available sources. Auto-activates on every command.
    9 repo stars