All authors

Claude Skills by kdlbs
github.com/kdlbs47 skills2 installs105 views
- Kandev Team AdminManage the Office roster when delegating work, hiring agents, changing budgets or concurrency, retiring agents, or checking spend before approvals.Votes: 0GitHub stars: 905
- Acp DebugDebug an ACP agent CLI by spawning it, speaking raw JSON-RPC, and capturing every frame to a JSONL file. Use when the user asks to probe an agent's capabilities, compare agents, test a prompt against an agent, inspect raw ACP wire frames, or investigate why an agent fails to initialize.Votes: 0GitHub stars: 901
- Add IntegrationAdd a new third-party integration (Jira/Linear-style) — per-workspace credentials, 90s auth-health poller, settings page, link/import buttons. Use when scaffolding a new external service integration.Votes: 0GitHub stars: 901
- Clean BranchesDelete local branches whose remote has been deleted ([gone]), including their worktrees. Use for branch cleanup after merging PRs.Votes: 0GitHub stars: 901
- Code ReviewReview changed code for quality, security, and architecture compliance. Use only when the user explicitly requests local review or a PR finding requires it.Votes: 0GitHub stars: 901
- CommitStage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says "commit", or before pushing a PR.Votes: 0GitHub stars: 901
- E2eWrite and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.Votes: 0GitHub stars: 901
- FixDiagnose a Kandev bug, reconcile its requirements and system design, create a reviewable fix plan and work orders, then hand off for explicit TDD implementation.Votes: 0GitHub stars: 901
- Mobile ParityEnsures Kandev UI work uses native mobile interaction patterns instead of compressed desktop adaptations while preserving desktop/mobile capability parity, responsive behavior, and mobile Playwright E2E coverage. Use when implementing, planning, reviewing, or testing any new feature, page, component, workflow, form, dialog, sidebar, navigation, dashboard, or visual UI change; if work touches frontend or user-facing UI, this skill must run even when user mentions only desktop or says "new feat...Votes: 0GitHub stars: 901
- PlanCreate an implementation plan and work orders from approved requirements and current system designs. Leave the design package uncommitted for review before implementation.Votes: 0GitHub stars: 901
- Playwright CliAutomate browser interactions, test web pages and work with Playwright tests.Votes: 0GitHub stars: 901
- Pr FixupWait for CI and automated reviews on a PR, fix valid failures and comments, disposition every review thread, verify, and push in the primary conversation.Votes: 0GitHub stars: 901
- PrCreate a PR from a committed and pushed branch after task-defined checks pass. Ready PRs continue to fixup in the primary conversation.Votes: 0GitHub stars: 901
- PushPush a committed branch whose task-defined checks passed. With --fixup, continue with CI and review handling in the primary conversation.Votes: 0GitHub stars: 901
- QaVerify a feature works after implementation. Actively try to break it — edge cases, error paths, integration wiring, and real usage flows.Votes: 0GitHub stars: 901
- RecordKeep durable architecture decisions, requirements, and system designs in sync. Auto-invoke when a request establishes or changes a long-lived boundary, public contract, ownership rule, operational invariant, or repo-wide convention with meaningful alternatives. Also use for explicit ADR or specification-recording requests.Votes: 0GitHub stars: 901
- ReleaseKandev release and version-channel conventions — unified Stable SemVer plus deterministic npm-only Nightlies. Use when cutting a release, changing channels, debugging artifacts, or answering version-channel questions.Votes: 0GitHub stars: 901
- SimplifySimplify recently changed code — inline one-off abstractions, remove speculative code, reduce nesting, replace cleverness with clarity. Run after implementing a feature.Votes: 0GitHub stars: 901
- SpecCreate or update Kandev product requirements and system-design documents before implementation. Use for new product behavior, changed contracts, or explicit specification work. Do not use for implementation plans, work orders, incidents, or behavior-preserving refactors.Votes: 0GitHub stars: 901
- TddImplement changes using Test-Driven Development (Red-Green-Refactor). Use for code changes that need coverage or requested test-value audits.Votes: 0GitHub stars: 901
- VerifyRun a broad local verification audit only when the user explicitly requests it or PR/CI remediation requires it.Votes: 0GitHub stars: 901
- Kandev ApprovalsList pending approvals and decide them (approve or reject)Votes: 0GitHub stars: 901
- Kandev EscalationHow to create a human-actionable decision task when you are blockedVotes: 0GitHub stars: 901
- Kandev ProtocolHow to interact with the kandev orchestrator via the CLIVotes: 0GitHub stars: 901
- Kandev RoutinesSchedule recurring work via cron and webhook triggersVotes: 0GitHub stars: 901
- MemoryRead and write persistent memory entries via agentctlVotes: 0GitHub stars: 901
- Context EngineeringCurate the right project context before coding or debugging. Use when starting a new session, switching areas of the codebase, output quality is drifting, a task spans backend/frontend/docs, or external instructions need to be reconciled with Kandev conventions.Votes: 0GitHub stars: 901
- Create Kandev PluginCreate, modify, debug, test, package, or publish a Kandev runtime plugin in its dedicated repository. Use only when the requested work targets a Kandev plugin implementation or its release and marketplace lifecycle, including fixing a bug in an existing plugin. Do not use for agent skills, MCP servers, general integrations, or Kandev host, SDK, loader, and registry changes that do not also change a plugin.Votes: 0GitHub stars: 901
- DebugDiagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix for code changes.Votes: 0GitHub stars: 901
- Docs MaintainerKeep public Kandev docs current when code or behavior changes affect CLI commands, config keys, install/deploy flows, workflows, executors, APIs, screenshots, or user-facing terminology. Use this before finishing any change with public documentation impact, and when reviewing whether a change needs docs.Votes: 0GitHub stars: 901
- Harness ImprovementImprove Kandev's AI harness from session learnings or explicit requests. Use when the user asks to record learnings, update or create skills, agents, subagents, commands, AGENTS.md/CLAUDE.md guidance, or adapt harness files across Claude, Codex, Cursor, or OpenCode.Votes: 0GitHub stars: 901
- Interview MeClarify a standalone idea or check assumptions before feature or fix planning. Use focused questions, stress-test intent, and map unresolved decisions for large uncertain initiatives.Votes: 0GitHub stars: 901
- Planner OrchestrationEnforce Kandev's single-session, user-controlled model workflow for feature, fix, debug, review, verification, and delivery work.Votes: 0GitHub stars: 901
- Pr WalkthroughGenerate a single-file HTML walkthrough that explains a PR's purpose, user impact, interface changes, compatibility risks, and implementation. Use for requests to generate a PR walkthrough or explain a PR visually. Not for code review, review findings, or approval verdicts.Votes: 0GitHub stars: 901
- Product Demo SeedingSeed coherent, disposable Kandev demo scenarios for screenshots, product films, landing-page media, and reproducible UI captures. Use when media needs believable tasks, workflows, agents, executors, integrations, plans, sessions, diffs, reviews, or native-mobile states; invoke before product-video-capture and never use a developer's main instance or data.Votes: 0GitHub stars: 901
- Product Video CaptureRecord, camera-process, encode, stage, and validate polished Kandev product films, landing-page loops, screenshots, and alternate framing from isolated demo data. Use when the user asks for product videos, GIF-like feature demos, cursor-follow camera motion, desktop/mobile captures, recaptures, landing media, or different framing; always invoke product-demo-seeding first.Votes: 0GitHub stars: 901
- Runtime Feature FlagsAdd, roll out, promote, graduate, or remove Kandev runtime feature flags and release toggles across the backend and frontend. Use whenever a task mentions a feature flag, release toggle, staged rollout, kill switch, or graduating a flag.Votes: 0GitHub stars: 901
- Spec Driven DevelopmentSingle-session Kandev feature workflow: clarify intent, create durable requirements, system designs, plans, and work orders, then hand off before implementation and verification.Votes: 0GitHub stars: 901
- Using Agent SkillsDiscover and choose the right Kandev agent skill for a task. Use when starting a session, when the user asks which skill applies, when work spans multiple phases, or when existing skill references need to be mapped to this repo's actual skills.Votes: 0GitHub stars: 901
- Kandev Config SyncSynchronize Office workspace configuration with the .kandev folder when exporting reviewable config, importing committed config, seeding a workspace, or reviewing a config diff.Votes: 0GitHub stars: 901
- Kandev ProjectsList and create Office projects, then place new tasks in the correct project when organizing workspace work by repository.Votes: 0GitHub stars: 901
- Kandev Task OpsOperate Office tasks when you need to list workspace tasks, read a conversation, or post an agent-authored comment.Votes: 0GitHub stars: 901
- Diagram DesignCreate branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, bar, line, Gantt and scatter charts, high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, deployment, dependency graph, UML class, story map, or database s...Votes: 0GitHub stars: 901
- FilesAuthor a Kandev task canvas as a self-contained web application.Votes: 0GitHub stars: 901
- Kandev Step DecisionRecord the current workflow step decision through the task-bound Office CLI.Votes: 0GitHub stars: 901
- Office Decision Cli TransportTeach decision-seat holders the CLI contract through a bundled system skill. Select that skill from the seat-derived advisory action and make the review and approval prompts require the command as their final action.Votes: 0GitHub stars: 901
- RetroUse when the user runs /retro or explicitly requests a session retrospective. Find session lessons and propose concrete shared harness edits for future efficiency. Exclude memory files. Do not run unprompted.Votes: 0GitHub stars: 901