arkaos 4.7.1 → 4.9.0

package/departments/community/skills/business-model/SKILL.md

@@ -1,8 +1,15 @@
 ---
 name: community/business-model
 description: >
-  Design a community business model: purpose, ideal member, value proposition,
-  monetization, platform selection, and growth strategy.
+  Designs a community business model with the Community BMC + SPACES
+  framework: purpose, ideal member, value proposition, engagement model,
+  monetization streams, retention, platform, and 1000-true-fans math.
+  TRIGGER: "modelo de negócio da comunidade", "como ganhar dinheiro com a
+  comunidade", "community business model", "is my community viable",
+  "/community model <niche>". SKIP: company or product business model
+  canvas -> strat/bmc (general BMC, not community); executing the revenue
+  plan -> community/monetize-plan; full launch package ->
+  community/niche-setup.
 allowed-tools: [Read, Write, Edit, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/content-calendar/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: community/content-calendar
 description: >
-  Community content calendar: daily prompts, weekly events, monthly themes.
+  Community content calendar: daily discussion prompts, weekly events, and
+  monthly themes, delivered with engagement triggers and an event schedule.
+  TRIGGER: "calendário de conteúdo da comunidade", "o que postar no grupo",
+  "community content calendar", "daily prompts for Discord", "planeia os
+  posts da comunidade", "/community calendar <period>". SKIP: creator or
+  multi-channel publishing calendar -> content/calendar (content business
+  pipeline); marketing campaign calendar -> mkt/calendar-plan; designing one
+  event in depth -> community/events-plan.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/events-plan/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: community/events-plan
 description: >
-  Event planning: AMA, workshop, challenge, co-working, launch party.
+  Plans a community event — AMA, workshop, challenge, co-working session, or
+  launch party — with format, agenda, promotion, and follow-up sequence.
+  TRIGGER: "organiza um AMA", "evento para a comunidade", "community event",
+  "plan a workshop for members", "desafio de 30 dias no grupo",
+  "/community event <type>". SKIP: recurring event cadence across
+  weeks/months -> community/content-calendar (owns the schedule, this owns
+  one event); events as a revenue stream -> community/monetize-plan.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/gamification-design/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: community/gamification-design
 description: >
-  Design gamification: points, levels, badges, leaderboards, challenges.
+  Designs community gamification with the Octalysis framework (Yu-kai Chou):
+  points, levels, badges, leaderboards, and challenges, delivered as a
+  mechanics and rewards spec with engagement loop design. TRIGGER: "gamifica
+  a comunidade", "sistema de pontos e badges", "gamification", "leaderboard
+  for my Discord", "níveis para membros", "/community gamify". SKIP:
+  gamification as one lever inside churn prevention ->
+  community/retention-system (owns the full lifecycle loop); measuring
+  whether engagement actually moved -> community/metrics-track.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/metrics-track/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: community/metrics-track
 description: >
-  Community metrics: DAU/MAU, engagement rate, churn, NPS, revenue per member.
+  Tracks community health metrics — DAU/MAU, engagement rate, churn, NPS,
+  revenue per member — delivered as a traffic-light health dashboard.
+  TRIGGER: "métricas da comunidade", "a comunidade está saudável?",
+  "community metrics", "engagement rate do Discord", "track member churn",
+  "/community metrics". SKIP: acting on churn signals ->
+  community/retention-system (interventions, not measurement); SaaS product
+  metrics (MRR, NRR, activation) -> saas/metrics-dashboard; business ops
+  dashboards -> ops/metrics-dashboard.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/moderation/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: community/moderation
 description: >
-  Moderation system: rules, escalation paths, automated filters, ban policies.
+  Builds a community moderation system: rules, escalation paths, automated
+  filters, and ban policies, delivered as a moderation playbook with
+  consequences and escalation matrix. TRIGGER: "modera a comunidade",
+  "regras do grupo", "moderation rules", "ban policy", "spam no Discord",
+  "escalation path para moderadores", "/community moderate". SKIP: welcoming
+  and activating new members -> community/onboarding-flow (positive
+  first-days path, not enforcement); overall engagement design ->
+  community/retention-system.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/monetize-plan/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: community/monetize-plan
 description: >
-  Community monetization: membership, courses, coaching, events, affiliate, sponsors, digital.
+  Community monetization plan across the 7-stream stack — membership,
+  courses, coaching, events, affiliate, sponsorships, digital products —
+  with revenue projections per stream. TRIGGER: "monetiza a comunidade",
+  "ganhar dinheiro com o grupo", "community monetization", "membership
+  pricing", "sponsors para a comunidade", "/community monetize". SKIP: SaaS
+  product pricing -> saas/pricing-strategy (product tiers, not community
+  streams); creator/content revenue -> content/monetization-plan; the full
+  viability question -> community/business-model.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/niche-setup/SKILL.md

@@ -1,7 +1,15 @@
 ---
 name: community/niche-setup
 description: >
-  Full niche community setup: business model, platform, content, monetization.
+  Full niche community setup end-to-end — business model, platform choice,
+  content plan, and monetization — delivered as a complete launch-ready
+  blueprint. TRIGGER: "cria uma comunidade de <nicho>", "lança a minha
+  comunidade", "start a community from scratch", "setup de comunidade paga",
+  "build a paid community", "/community setup <niche>". SKIP: AI/tech
+  Discord vertical -> community/ai-community; betting/trading Telegram
+  vertical -> community/betting-setup; only one piece needed ->
+  community/platform-select, community/monetize-plan, or
+  community/business-model.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/onboarding-flow/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: community/onboarding-flow
 description: >
-  Design member onboarding: welcome DM, first 7 days, activation triggers.
+  Designs member onboarding with the Member Lifecycle (Millington): welcome
+  DM, first-7-days journey, activation triggers, automated messages, and
+  milestones with activation metrics. TRIGGER: "onboarding de membros",
+  "primeiros dias na comunidade", "welcome new members", "member
+  activation", "mensagem de boas-vindas automática", "/community onboard".
+  SKIP: SaaS product user onboarding -> saas/onboarding-optimize (product
+  activation, not community); keeping existing members engaged past week
+  one -> community/retention-system.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/platform-select/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: community/platform-select
 description: >
-  Select the right platform for your niche: Telegram, Discord, Skool, Circle, Mighty, Whop.
+  Selects the right community platform for a niche — Telegram, Discord,
+  Skool, Circle, Mighty, Whop — via a selection matrix, delivered as a
+  recommendation with comparison table and migration plan. TRIGGER: "que
+  plataforma para a comunidade", "Discord ou Telegram?", "Skool vs Circle",
+  "where should I host my community", "migrar a comunidade de plataforma",
+  "/community platform <niche>". SKIP: platform already chosen and needs
+  setup -> community/niche-setup (or community/ai-community for AI Discord);
+  viability question first -> community/business-model.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/community/skills/retention-system/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: community/retention-system
 description: >
-  Design member retention system with engagement loops, gamification,
-  and churn prevention triggers.
+  Designs a member retention system: 6-stage lifecycle triggers, 7 retention
+  habits, churn-signal responses (7/14/30-day win-backs), and gamification
+  elements. TRIGGER: "reter membros", "os membros estão a sair", "member
+  retention", "reduce community churn", "engagement loops", "win-back de
+  membros", "/community retain". SKIP: SaaS revenue churn diagnosis ->
+  saas/churn-analysis (cohorts and MRR, not members); designing the
+  points/badges system itself -> community/gamification-design; measuring
+  health -> community/metrics-track.
 allowed-tools: [Read, Write, Edit, Agent]
 ---
 

package/departments/content/skills/ai-workflow/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: content/ai-workflow
 description: >
-  AI content workflow: ideation, drafting, editing, formatting with AI assistance.
+  AI-augmented content workflow: ideation, drafting, editing, and formatting
+  with AI assistance plus human review checkpoints. TRIGGER: "usa AI para
+  criar conteúdo", "draft this with AI", "AI content workflow", "edita este
+  rascunho com AI", "acelera a produção de conteúdo", "/content ai". SKIP:
+  building the full pillar-to-derivatives operating system ->
+  content/content-system (owns strategy and cadence, not AI-assisted
+  drafting); automating business processes or integrations ->
+  ops/workflow-automate (non-content automation).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/analytics/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: content/analytics
 description: >
-  Content analytics: views, engagement, saves, shares, CTR, revenue attribution.
+  Content performance analytics: views, engagement, saves, shares, CTR, and
+  revenue attribution, delivered as a report with top/bottom performers and
+  optimization actions. TRIGGER: "como está a performance do conteúdo",
+  "content analytics", "quais posts tiveram mais engagement", "analisa as
+  views", "revenue por conteúdo", "/content analytics". SKIP: cross-channel
+  campaign metrics -> marketing/analytics-report (owns campaign reporting);
+  page-to-purchase conversion metrics -> landing/funnel-metrics (owns funnel
+  conversion, not content engagement).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/calendar/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: content/calendar
 description: >
-  Content calendar: weekly themes, pillar assignments, derivative scheduling.
+  Content calendar planning: weekly themes, pillar assignments, and derivative
+  scheduling mapped from pillar to platform-native pieces. TRIGGER:
+  "calendário de conteúdo", "content calendar", "planeia a semana de posts",
+  "publishing schedule", "agenda de publicações", "/content calendar". SKIP:
+  campaign and promo timing across channels -> marketing/calendar-plan (owns
+  marketing campaign calendars); community-space programming ->
+  community/content-calendar (owns community engagement calendars); building
+  the whole strategy, not one calendar -> content/content-system.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/content-system/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: content/content-system
 description: >
-  Set up a Content Operating System: pillar content strategy, batching workflow,
-  1-to-30+ repurposing pipeline, calendar, and analytics tracking.
+  Sets up a full Content Operating System: pillar content strategy (GaryVee
+  model), weekly batching workflow, 1-to-30+ repurposing pipeline, calendar
+  template, and metrics tracking. TRIGGER: "monta o meu sistema de conteúdo",
+  "content operating system", "estratégia de conteúdo completa", "pillar
+  content strategy", "content OS", "/content system". SKIP: only scheduling an
+  existing strategy -> content/calendar (one calendar, not the system); only
+  atomizing one piece -> content/repurpose-plan (single pillar, not the
+  operating system).
 allowed-tools: [Read, Write, Edit, Agent, WebFetch]
 ---
 

package/departments/content/skills/hook-write/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: content/hook-write
 description: >
-  Write hooks for the first 3 seconds of any content. 7 hook types with
-  templates and A/B testing variants.
+  Writes hooks for the first 3 seconds of any content: generates 10+ variants
+  across 7 hook types (controversy, curiosity gap, pain point, result,
+  counter-intuitive, story, direct value), scores them, and formats the top 5
+  per platform. TRIGGER: "hook para reels", "escreve um hook", "opening
+  line", "primeiros 3 segundos", "hook for TikTok", "/content hook". SKIP:
+  headlines for landing pages or sales copy -> landing/headline-write
+  (conversion copy, not retention hooks); full video script ->
+  content/script-structure.
 allowed-tools: [Read, Write, Edit, Agent]
 ---
 

package/departments/content/skills/monetization-plan/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: content/monetization-plan
 description: >
-  Creator monetization plan: 5 levels from ads to high-ticket.
+  Creator monetization plan: a 5-level ladder from ads and affiliates up to
+  high-ticket offers, with revenue projections per level. TRIGGER: "como
+  monetizar o meu conteúdo", "monetize my audience", "plano de monetização",
+  "creator revenue streams", "ganhar dinheiro com o canal", "/content
+  monetize". SKIP: monetizing a community or membership ->
+  community/monetize-plan (owns community revenue models); recurring product
+  pricing -> ecom/subscription-model (product pricing, not the creator
+  ladder).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/newsletter-write/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: content/newsletter-write
 description: >
-  Newsletter writing: subject line, intro hook, sections, CTA, growth tactics.
+  Newsletter writing: subject line variants, intro hook, body sections, CTA,
+  and growth tactics, delivered as a ready-to-send draft with growth
+  recommendations. TRIGGER: "escreve a newsletter", "newsletter desta
+  semana", "write a newsletter issue", "subject line para email", "edição da
+  newsletter", "/content newsletter". SKIP: automated multi-email nurture or
+  sales sequences -> marketing/email-sequence (funnel automation, not
+  editorial issues); cold outbound prospecting email -> marketing/cold-email.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/platform-optimize/SKILL.md

@@ -1,7 +1,15 @@
 ---
 name: content/platform-optimize
 description: >
-  Platform-specific optimization: signals, formats, timing per algorithm.
+  Platform-specific content optimization: algorithm signals, best-performing
+  formats, and posting times for a given platform, delivered as a platform
+  guide. TRIGGER: "otimiza para o Instagram", "how does the TikTok algorithm
+  work", "melhor hora para publicar", "platform algorithm", "formatos que
+  funcionam no LinkedIn", "/content platform". SKIP: choosing WHICH platform
+  to build a community on -> community/platform-select (platform choice, not
+  optimization); overall social channel strategy -> marketing/social-strategy;
+  YouTube specifically -> content/youtube-strategy (dedicated deeper
+  playbook).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/repurpose-plan/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: content/repurpose-plan
 description: >
-  Repurpose one pillar piece into 30+ platform-native content pieces.
+  Repurposes one pillar piece into 30+ platform-native derivatives (clips,
+  posts, threads, carousels, newsletter sections) with a scheduling map.
+  TRIGGER: "reaproveita este vídeo", "repurpose this post", "transforma em
+  reels", "atomize my content", "derivados deste artigo", "/content
+  repurpose". SKIP: designing the whole pillar strategy and cadence ->
+  content/content-system (the system that produces pillars, not one piece);
+  scheduling already-made pieces -> content/calendar.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/script-structure/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: content/script-structure
 description: >
-  Long-form script: YouTube, podcast, webinar with retention techniques.
+  Long-form script writing for YouTube, podcast, or webinar: full script with
+  timestamps, hooks, transitions, retention techniques, and CTA placement
+  (Hook-Bridge-Body-CTA). TRIGGER: "escreve o guião do vídeo", "video
+  script", "script para o podcast", "roteiro longo", "webinar script",
+  "/content script-long". SKIP: sub-60-second vertical video ->
+  content/short-form (short-form scripts and algorithm formatting);
+  channel-level positioning and packaging -> content/youtube-strategy; just
+  the opening seconds -> content/hook-write.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/short-form/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: content/short-form
 description: >
-  Short-form content: Reels, TikTok, Shorts optimized for each platform's algorithm.
+  Short-form content creation: 5 Reels/TikTok/Shorts scripts with hooks,
+  platform-native formatting, and a posting schedule, optimized for each
+  platform's algorithm. TRIGGER: "cria uns reels", "TikTok script", "ideias
+  para shorts", "conteúdo curto", "vertical video", "/content short". SKIP:
+  10+ minute video or podcast script -> content/script-structure (long-form
+  retention structure); engineering shareability of a piece ->
+  content/viral-design (STEPPS scoring, not production); hooks alone ->
+  content/hook-write.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/thumbnail-package/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: content/thumbnail-package
 description: >
-  Thumbnail and title packaging: 5+ variants for A/B testing.
+  Thumbnail and title packaging (MrBeast method): 5+ title/thumbnail variants
+  for A/B testing with curiosity-gap scoring. TRIGGER: "faz a thumbnail",
+  "thumbnail ideas", "título para o vídeo", "video title and thumbnail",
+  "packaging do vídeo", "/content thumbnail". SKIP: full channel strategy
+  where packaging is one of seven deliverables -> content/youtube-strategy;
+  spoken or written hooks for the content itself -> content/hook-write;
+  actual image asset production -> brand/mockup-generate (visual design
+  execution).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/viral-design/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: content/viral-design
 description: >
-  Design viral content using Jonah Berger's STEPPS framework. Score content
-  against 6 viral triggers before publishing.
+  Designs viral content with Jonah Berger's STEPPS framework: scores topic
+  and final piece against the 6 triggers (Social Currency, Triggers, Emotion,
+  Public, Practical Value, Stories), minimum 6/12 to publish. TRIGGER:
+  "conteúdo viral", "make this go viral", "porque não viralizou", "viral
+  content ideas", "quero que isto seja partilhado", "/content viral". SKIP:
+  producing the actual short-form scripts -> content/short-form (production,
+  not virality scoring); only the opening hook -> content/hook-write (hooks
+  are one step of this flow).
 allowed-tools: [Read, Write, Edit, Agent, WebFetch, WebSearch]
 ---
 

package/departments/content/skills/youtube-strategy/SKILL.md

@@ -1,9 +1,15 @@
 ---
 name: content/youtube-strategy
 description: >
-  YouTube strategy — channel positioning, title × thumbnail architecture,
-  hook + script structure, SEO + metadata, publishing cadence, cross-platform
-  distribution.
+  Full YouTube channel strategy in 7 deliverables: channel positioning, 10
+  title-thumbnail pairs, hook architecture, retention-mapped script
+  structure, SEO metadata stack, 90-day publishing cadence, and
+  cross-platform derivative spec. TRIGGER: "estratégia para o YouTube", "grow
+  my YouTube channel", "lançar canal de YouTube", "YouTube SEO", "CTR e
+  retenção", "/content youtube". SKIP: one video's packaging only ->
+  content/thumbnail-package; one video's script only ->
+  content/script-structure; Shorts-only content -> content/short-form
+  (vertical short-form, not channel strategy).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/dev/skills/agent-design/SKILL.md

@@ -1,8 +1,15 @@
 ---
 name: dev/agent-design
 description: >
-  Design multi-agent architectures with role definitions, communication patterns,
-  tool schemas, guardrails, and evaluation frameworks.
+  Design multi-agent system architectures — supervisor/swarm/pipeline
+  patterns, agent role definitions, tool schemas, communication patterns,
+  guardrails, and memory design (Multi-Agent Architecture Patterns). TRIGGER:
+  "agent design", "desenha um sistema de agentes", "multi-agent architecture",
+  "arquitetura de agentes", "define agent roles", "/dev agent-design"; load
+  BEFORE building any agent system. SKIP: wiring an existing set of agents
+  into a flow with handoffs and failure policies -> dev/agent-workflow (it
+  designs the FLOW; this designs the AGENTS); non-agent system architecture ->
+  dev/architecture-design.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/dev/skills/agent-workflow/SKILL.md

@@ -1,8 +1,15 @@
 ---
 name: dev/agent-workflow
 description: >
-  Design production-grade multi-agent workflows with pattern selection,
-  handoff contracts, failure handling, and cost/context controls.
+  Design production-grade multi-agent workflows — pattern selection
+  (sequential, parallel, router, orchestrator, evaluator), handoff contracts,
+  validation gates, failure handling, and cost/context budgets (Workflow
+  Orchestration Patterns). TRIGGER: "agent workflow", "orquestra os agentes",
+  "workflow de agentes", "handoff between agents", "pipeline de subagents",
+  "/dev agent-workflow"; load BEFORE implementing orchestration code. SKIP:
+  defining the agents themselves (roles, tools, guardrails, memory) ->
+  dev/agent-design (it shapes the AGENTS; this wires the FLOW); one-off
+  complex task planning -> /arka-forge.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/dev/skills/ai-assisted-dev/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: dev/ai-assisted-dev
 description: >
-  AI-assisted development: prompt engineering for code, review AI output, TDD with AI.
+  AI-assisted development practice: prompt engineering for code generation,
+  structured review of AI output, and TDD with AI in the loop. TRIGGER: "ai
+  dev", "prompt engineering", "gera código com IA", "review AI output",
+  "programar com IA", "code with AI", "/dev ai-dev". SKIP: securing AI/LLM
+  systems (prompt injection, guardrails) -> dev/ai-security (assessment, not
+  development practice); building MCP servers -> dev/mcp-builder; plain TDD
+  without AI in the loop -> dev/tdd-cycle.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/dev/skills/ai-security/SKILL.md

@@ -1,8 +1,15 @@
 ---
 name: dev/ai-security
 description: >
-  AI/ML-specific security assessment: prompt injection, model poisoning,
-  data leakage, agent tool abuse, and MITRE ATLAS technique mapping.
+  AI/ML-specific security assessment with OWASP ML Top 10, NIST AI RMF, and
+  MITRE ATLAS technique mapping: prompt injection, jailbreaks, model
+  poisoning, data leakage, agent tool abuse, and guardrail design. TRIGGER:
+  "ai security", "prompt injection", "segurança do modelo", "jailbreak",
+  "guardrails", "audita o agente", "/dev ai-security". SKIP: general
+  application security (OWASP Top 10, headers, dependencies) ->
+  dev/security-audit (web/app scope, not models); vetting a third-party skill
+  before install -> dev/skill-audit; offensive engagement planning ->
+  dev/red-team.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/dev/skills/api-design/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: dev/api-design
 description: >
-  Design REST or GraphQL APIs with versioning, documentation, and contracts.
-  Follows OpenAPI spec for REST, SDL for GraphQL.
+  Design REST or GraphQL APIs with resource modeling, versioning, pagination,
+  error contracts, and documentation — OpenAPI 3 spec for REST, SDL for
+  GraphQL, Laravel conventions included. TRIGGER: "api design", "desenha a
+  API", "endpoints", "contrato da API", "REST", "GraphQL", "/dev api-design";
+  load BEFORE implementing controllers or routes. SKIP: system architecture
+  beyond the API surface -> dev/architecture-design; the database schema
+  behind the API -> dev/db-schema; requirements not yet defined -> dev/spec
+  first.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/dev/skills/app-test/SKILL.md

@@ -1,9 +1,13 @@
 ---
 name: dev/app-test
 description: >
-  Build, launch, and click through a native app (macOS or iOS Simulator).
-  Screenshot each screen, report crashes or visual issues.
-  Requires Computer Use (/mcp → computer-use).
+  Build, launch, and click through a native app (macOS or iOS Simulator) via
+  Computer Use — exercises every control systematically, screenshots each
+  screen, reports crashes and visual issues. TRIGGER: "app test", "testa a app
+  nativa", "test the macOS app", "iOS simulator", "clica pela app toda", "/dev
+  app-test"; requires Computer Use (/mcp -> computer-use). SKIP: web app flows
+  in a browser -> dev/demo-gif (browser recording, not native apps); writing
+  automated unit/feature tests -> dev/tdd-cycle.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/dev/skills/architecture-design/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: dev/architecture-design
 description: >
-  Design system architecture using Clean Architecture, Hexagonal, or DDD patterns.
-  Produces an ADR (Architecture Decision Record) saved to Obsidian.
+  Design system architecture with Clean Architecture, Hexagonal, or DDD
+  patterns and produce an ADR (Architecture Decision Record) saved to
+  Obsidian, approved by Marco (CTO). TRIGGER: "architecture", "arquitetura do
+  sistema", "ADR", "system design", "desenha a arquitetura", "clean
+  architecture", "/dev architecture"; load BEFORE large structural changes.
+  SKIP: deep domain modeling (bounded contexts, aggregates, events) ->
+  dev/ddd-model (strategic DDD detail); API contract design only ->
+  dev/api-design; feature requirements -> dev/spec.
 allowed-tools: [Read, Write, Edit, Grep, Glob, Agent, WebFetch]
 ---
 

package/departments/dev/skills/changelog/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: dev/changelog
 description: >
-  Generate changelogs from git history using conventional commits. Lint commit messages, detect version bumps, and render Keep a Changelog format.
+  Generate changelogs from git history using Conventional Commits: lints
+  commit messages, detects the SemVer bump (MAJOR/MINOR/PATCH), groups
+  entries, and renders Keep a Changelog format. TRIGGER: "changelog", "gera o
+  changelog", "release notes", "notas de versão", "what changed since the last
+  tag", "/dev changelog". SKIP: planning and executing the whole release
+  (readiness checklist, deploy sequence, rollback) -> dev/release (the
+  changelog is one artifact of it); shipping the deployment itself ->
+  dev/deploy.
 allowed-tools: [Read, Bash, Grep, Glob, Agent]
 ---
 

package/departments/dev/skills/ci-cd-pipeline/SKILL.md

@@ -1,8 +1,13 @@
 ---
 name: dev/ci-cd-pipeline
 description: >
-  Design and generate CI/CD pipelines from detected project stack.
-  GitHub Actions and GitLab CI with caching, matrix builds, and deployment gates.
+  Design and generate CI/CD pipelines from the detected project stack — GitHub
+  Actions or GitLab CI with lint/test/build/deploy stages, dependency caching,
+  matrix builds, and gated production deploys. TRIGGER: "ci/cd", "pipeline",
+  "github actions", "cria o pipeline", "gitlab ci", "automatiza os testes no
+  CI", "/dev ci-cd-pipeline". SKIP: deployment strategy design (blue-green,
+  canary, GitOps, monitoring) -> dev/devops-pipeline (strategy; this generates
+  the config); executing a deploy right now -> dev/deploy.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/dev/skills/codebase-onboard/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: dev/codebase-onboard
 description: >
-  Analyze an existing codebase and generate onboarding documentation: architecture, patterns, setup, key files.
+  Analyze an existing codebase and generate onboarding documentation for new
+  developers: stack detection, architecture map, patterns, setup instructions,
+  and key files, tuned to the audience (junior/senior/contractor). TRIGGER:
+  "onboarding docs", "explica este codebase", "how does this repo work",
+  "documenta a arquitetura para novos devs", "/dev codebase-onboard". SKIP:
+  registering a project into ARKA OS (PROJECT.md, MCPs, Obsidian pages) ->
+  dev/onboard (system registration, not human docs); general README/API doc
+  updates -> dev/docs.
 allowed-tools: [Read, Bash, Grep, Glob, Agent]
 ---