markus-global/markus

Goal Add a benchmark harness so we can measure Markus performance across releases: time-to-first-response, task completion latency, throughput (tasks/hour), and cost per task. Proposal scripts/benchmark/ with a benchmark scenario definition (e.g., 'draft a product summary' and 'fix a lint error') Runs a headless Markus instance against a real LLM (configurable provider, default small/cheap model) Emits JSON results (timestamps, model, token usage, duration) + a summary table CI optional: a monthly scheduled workflow posting results to an issue Reference files packages/cli/src/commands/start.ts (how the server boots) packages/core agent execution (task lifecycle timing hooks) vitest.config.ts (test setup patterns) Acceptance criteria Reproducible: same command, same inputs, documented env (model, temperature, cache) JSON output schema documented in scripts/benchmark/README.md Fails fast with clear messages when LLM keys are missing pnpm test / typecheck / lint pass Size: L · Skil

Goal Markus ships 25 role templates (templates/roles/): researcher, developer, reviewer, ops, finance, HR, SRE... Add a role we don't yet have, following the same structure. Candidate roles (pick one or propose your own with a clear job description) security-auditor (review code/arch for vulnerabilities) data-analyst (SQL/reporting agent) seo-specialist (web visibility) sales-engineer (demo + technical sales) localization-manager (i18n coordination) How Study templates/roles/sre/ROLE.md and templates/roles/secretary/ROLE.md — note the structure: Identity & Expertise, Core Responsibilities, Workflow, Guardrails, metrics Create templates/roles/NEW-ROLE/ROLE.md with: Identity section (who the agent is, core expertise) Core Responsibilities (tables of duties, triggers, outputs) Workflow steps Guardrails / escalation rules Concrete success metrics Add the role to the README package table if roles are listed there Validate: the role directory is discoverable by the agent system (see

Goal Windows users currently must install via npm or the Electron desktop package. Add a PowerShell installer (iwr -UseBasicParsing ... | iex) that mirrors scripts/install.sh: detect architecture, download the right binary bundle, verify checksum, and print next steps. Reference files scripts/install.sh (existing bash installer — mirror its logic) scripts/build-binary.sh (what artifacts exist for Windows) markus.global/install.sh endpoint (where the script is served) Acceptance criteria install.ps1 works on PowerShell 5.1+ and 7+ (x64 + arm64) Downloads and verifies checksum, installs to %LOCALAPPDATA%\Markus (or similar), adds to PATH Documented in README Quick Start (Windows line) No secrets; respects standard security (RemoteSigned / execution policy guidance) Size: M · Skill needed: PowerShell, release engineering · Comment before starting to coordinate with release automation.

Goal Extend markus skill import to normalize more external skill formats. Current support: skills.sh / Claude Code, SkillHub / ClawHub, OpenClaw, SOUL.md, AgentScope, MCP servers (see docs/SKILL-ECOSYSTEM.md). Candidate formats (pick one or propose another with community traction) OpenAI GPTs / Actions Dify plugins Cursor Rules / .cursor/rules n8n workflow nodes AutoGPT / A2A agent definitions How Read docs/SKILL-ECOSYSTEM.md §1-2 (supported formats + field mapping) and the import pipeline in packages/core (search for skill import in packages/core/src/skills/ or similar) Add a detector + normalizer for one new format, mapping its fields to the Markus skill manifest Export support is a bonus: markus skill export --format NAME Reference files docs/SKILL-ECOSYSTEM.md packages/core skill import/export code (CLI: markus skill import/export) Acceptance criteria New format auto-detected by markus skill import Round-trip metadata preserved (name, description, tools, permissions) Unit t

Goal Add a Discord messaging adapter to packages/comms so teams can drive Markus from Discord. This also enables the planned Discord community channel. How Follow the existing adapter pattern — each adapter lives in packages/comms/src/NAME/ with adapter.ts + client.ts and is wired in packages/comms/src/router.ts: Study packages/comms/src/telegram/ (which is similar in shape) and packages/comms/src/slack/ Implement a minimal Discord client (discord.js or raw REST) supporting: receive messages, send messages, connect/disconnect Register the adapter in packages/comms/src/index.ts + router.ts Add unit tests mirroring packages/comms/test/telegram-adapter.test.ts Reference files packages/comms/src/telegram/, slack/, router.ts, index.ts packages/comms/test/telegram-adapter.test.ts Acceptance criteria discord.js (or equivalent) is a peerDependency, not bundled into core Adapter connects, receives, and sends with graceful error handling (token invalid, network down) Unit tests pass; pnpm