Showing 30 of 27361 results
Technical-writing & docs team โ 3 agents (docs-architect, api-reference-writer, docs-site-engineer) for developer and product documentation that people actually use: the Diataxis framework (tutorial / how-to / reference / explanation โ and not mixing them), docs-as-code (docs in the repo, reviewed and CI-checked, versioned with the product), accurate API/SDK reference (spec-driven, examples that run, errors documented), and a maintainable docs site (Docusaurus/Mintlify/MkDocs, IA, search, versioning). Deepens ravenclaude-core/documentarian. 5 skills, a decision-tree knowledge bank (doc-type, docs-tooling, Diataxis content-type, lint-in-CI-vs-manual + a dated 2026 map), a 4-scenario bank, 12 best-practices, 4 templates, 4 commands, 1 advisory hook, a prose-linter LSP tier (Vale-LS + Marksman) and a stdlib readability/prose checker. Seams: dev portal/SDK -> api-engineering, site design -> web-design, prose polish -> ravenclaude-core/documentarian. Requires ravenclaude-core@>=0.7.0.
Technical writing techniques with strict templates: design-review-writer (interactive discovery โ fixed-template Design Review) and adr-writer (declarative Architecture Decision Record derived from a Design Review or raw context).
Manage Technitium DNS Server instances โ configure, query stats, manage zones and records, and control DNS blocking with per-domain allow/block overrides and block list URLs.
Architecture, engineering delivery, development discipline, debugging, review, and AI and automation systems.
Adapts explanation depth based on user proficiency per technology: expert, intermediate, or learning
Build and maintain technology radars for adoption, trial, assessment, and hold decisions, and choose proportionate architecture-governance paths for technology portfolios. Use when governing technology choices, build-versus-buy decisions, architecture standards, exceptions, or engineering portfolio risk. Do not use for enterprise capability or target-state architecture, writing ADRs, implementing systems, security engineering, or operational incident/runbook work.
Techonomy-branded skills voor client deliverables: campagneplan presentaties, mediaplannen en meer.
Techonomy-branded skills voor client deliverables: campagneplan presentaties, mediaplannen en meer.
Techonomy-branded skills voor client deliverables: campagneplan presentaties, mediaplannen en meer.
Claude Code skill pack for TechSmith (18 skills)
Core development lifecycle skills for implementing features, fixing bugs, refactoring, managing git, database migrations, dependencies, and codebase quality.
Validate a software project against TEHIK's published standards documents. Each skill splits its source document across parallel subagents to keep context manageable and produces a Markdown audit report with per-requirement verdicts and recommendations.
Folder-based task board pipeline skills for turning business briefs into tasks, processing queues, running task workflows, and second-pass validation.
Telegram channel for Claude Code โ messaging bridge with built-in access control, pairing, and full Bot API coverage including voice note transcription.
cc-bridge โ drive Claude Code from Telegram. Built-in access control; manage pairing, allowlists, and policy via /telegram:access.
Telegram messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.
Telegram Bridge MCP skill library by Electrified Cortex
from kairos03/telegram-notifier
Push a Telegram message when a Claude Code session finishes a turn, ends on a question, or needs your attention. Cross-platform, multi-account aware, optional LLM summaries.
Telegram channel for Claude Code: one bot, many Claude sessions, forum topics / DMs bind to project folders via /bind, tmux ops (/compact, /restart, /resume, /new, /status). Linux & macOS.
Telegram Bot API ใฎ long-polling ใ cloud routine ไธใงๅธธ้งใใใ่ชๅฏๆธใฟใใฃใใใใใฎใกใใปใผใธใซ็งๆธใจใผใธใงใณใ๏ผSecretaryRole๏ผใๅณๅฟใใๅฏพ่ฉฑใใฃใใซ
Give each agent a key scoped to one job that can only narrow, never widen. A prompt-injected agent reaches for a capability it was never given โ the call is blocked before it runs. Enforced on every tool call via a PreToolUse hook.
Operate the observability stack that deploys as one unit: Prometheus scrape configuration, recording and alerting rules, relabeling, retention, and high availability; OpenTelemetry Collector pipelines (receivers, processors, exporters, sampling, trace/span correlation); and Loki ingest, LogQL, retention, and label design โ with a bundled read-only telemetry-check script for Prometheus rule sanity and scrape-target reachability. Use when running, tuning, or troubleshooting a Prometheus, OpenTelemetry Collector, or Loki deployment, or reviewing the collection/ingest/retention layer. Do not use for observability strategy, SLI/SLO design, or paging policy (that is platform-engineering) or Grafana dashboards, panels, and Grafana-side alerting (that is grafana).
Review your own Claude Code sessions from Langfuse traces and turn findings into config improvements