weorbitant
- 68 skills
- 0 followers
- 4 hours ago last updated
- ▌ New Learning · weorbitantUse 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".
- ▌ Learning Status · weorbitantUse 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".
- ▌ Learning Insights · weorbitantInternal-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.
- ▌ Blog Post Review · weorbitant bundleEditorial 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.
- ▌ Learn · weorbitantUse 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".
- ▌ Debrief · weorbitantUse 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".
- ▌ End Learn · weorbitantUse 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".
- ▌ Init Learning · weorbitantUse 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.
- ▌ Learning Report · weorbitantUse 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".
- ▌ Infra Logs · weorbitantUse 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.
- ▌ Infra Pods · weorbitantUse 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".
- ▌ Infra Deploy · weorbitant bundleUse 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".
- ▌ Creating Skills · weorbitant bundleUse 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.
- ▌ Jira Create Bug · weorbitantUse 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".
- ▌ Infra Migrations · weorbitant bundleUse 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.
- ▌ Infra Portforward · weorbitant bundleUse 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.
- ▌ Jira Clarify Ticket · weorbitant bundleUse 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.
- ▌ Rabbitmq Triage Dlq · weorbitant bundleUse 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.
- ▌ Rabbitmq List Queues · weorbitantUse 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".
- ▌ Rabbitmq Reprocess Dlq · weorbitantUse 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".
- ▌ Adr · weorbitant bundleUse 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.
- ▌
- ▌
- ▌
- ▌ Create Bug · weorbitant bundleUse 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.
- ▌
- ▌ Notify Team · weorbitant bundleUse 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.
- ▌ Analyze Docs · weorbitant bundleUse 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.
- ▌
- ▌
- ▌
- ▌
- ▌ Sprint Review · weorbitant bundleUse 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.
- ▌
- ▌ Analyze Design · weorbitant bundleUse 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.
- ▌ Clarify Ticket · weorbitant bundleUse 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.
- ▌
- ▌ Ticket Analysis · weorbitant bundleUse 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.
- ▌
- ▌
- ▌ Board To Stories · weorbitant bundleUse 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.
- ▌ Analyze Data Model · weorbitantUse 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.
- ▌ Analyze Feasibility · weorbitantUse 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.
- ▌ Orbitant Release Notes · weorbitantDrafts 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.
- ▌ Skill Reviewer · weorbitantReviews 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.
- ▌ Orbitant Tone · weorbitantVoice 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.
- ▌ Orbitant Learn · weorbitantUse 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".
- ▌ Orbitant Debrief · weorbitantUse 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".
- ▌ Orbitant Newsletter · weorbitantDrafts 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.
- ▌ Orbitant 12 Factor · weorbitant bundleUse 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.
- ▌ Orbitant End Learn · weorbitantUse 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".
- ▌ Orbitant Owasp Scan · weorbitant bundleUse 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.
- ▌ Orbitant Git Hygiene · weorbitant bundleUse 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".
- ▌ Orbitant Linkedin Post · weorbitantLinkedIn 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.
- ▌ Orbitant AI Readiness · weorbitant bundleUse 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".
- ▌ Orbitant New Learning · weorbitantUse 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".
- ▌ Orbitant Image Creation · weorbitant bundleGenerates 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.
- ▌ Orbitant Yt Description · weorbitantYouTube 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.
- ▌ Orbitant Init Learning · weorbitantUse 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.
- ▌ Orbitant Goal Alignment · weorbitantScores items against quarterly rocks from rocks.yaml. Activates during triage, task ranking, meeting prep, and scheduling. Flags drift when time allocation mismatches stated priorities.
- ▌ Orbitant Voice Drafting · weorbitantWrites 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.
- ▌ Orbitant Blog Post Create · weorbitant bundleContent 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.
- ▌ Orbitant Blog Post Review · weorbitantEditorial 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".
- ▌ Orbitant Learning Report · weorbitantUse 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".
- ▌ Orbitant Learning Status · weorbitantUse 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".
- ▌ Orbitant Learning Insights · weorbitantInternal-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.
- ▌ Orbitant Blog Post Translate · weorbitantTranslation 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.
- ▌ Orbitant Graceful Degradation · weorbitantChecks 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.