Skills Directory
Claude Skills by tools-only
github.com/tools-onlyComplete reference for Obsidian's URI automation capabilities.
```dataview LIST FROM "folder" WHERE condition SORT field ASC/DESC LIMIT 10 ```
Quick reference for commonly used PromQL functions and patterns.
Complete reference for Robusta playbook triggers.
Executes Azure deployments using generated Bicep templates. Runs deploy.ps1 scripts, performs what-if analysis, and manages deployment lifecycle. Step 6 of the 7-step agentic workflow.
Executes Azure deployments using generated Bicep templates. Runs deploy.ps1 scripts, performs what-if analysis, and manages deployment lifecycle. Step 6 of the 7-step agentic workflow.
Executes Azure deployments using generated Bicep templates. Runs deploy.ps1 scripts, performs what-if analysis, and manages deployment lifecycle. Step 6 of the 7-step agentic workflow.
Executes Azure deployments using generated Bicep templates. Runs deploy.ps1 scripts, performs what-if analysis, and manages deployment lifecycle. Step 6 of the 7-step agentic workflow.
Executes Azure deployments using generated Bicep templates. Runs deploy.ps1 scripts, performs what-if analysis, and manages deployment lifecycle. Step 6 of the 7-step agentic workflow.
Executes Azure deployments using generated Bicep templates. Runs deploy.ps1 scripts, performs what-if analysis, and manages deployment lifecycle. Step 6 of the 7-step agentic workflow.
The plugin-creator refactor workflow (assessor → implement-refactor → start-refactor-task → ensure-complete) has 4 verified disconnects between steps. Identified by reading source files on 2026-02-09.
Task T19: Pre-commit Hook Update
Task T19: Pre-commit Hook Update
Task T20: Documentation Updates
Task T20: Documentation Updates
Task T22: Reference Updates (Comprehensive)
Task T22: Reference Updates (Comprehensive)
Task T7: ProgressiveDisclosureValidator
Task T7: ProgressiveDisclosureValidator
Display and manage Claude Copilot configuration settings, including ecomode thresholds, cost tracking preferences, and other framework settings.
**IMPORTANT: Always use OpenViking first for knowledge queries and memory storage**
| Practice | Why | |----------|-----| | Order by change frequency | Rarely-changing layers first (base, system packages), frequently-changing last | | Combine related RUN commands | Reduces layers and ensures cache coherence | | Clean up in same layer | Don't leave apt cache in a layer | | Use multi-stage builds | Separate build dependencies from runtime, reduce final image size | | Pin versions with digests | Supply chain security: `FROM alpine:3.21@sha256:abc123...` | | Switch to non-root user
Snap confinement creates separate filesystem namespaces. The CLI process and the running Obsidian instance end up with different `SingletonLock`/`SingletonSocket` paths, so CLI can't connect via IPC. The deb package avoids this entirely.
- **A股数据采集**：通过 TuShare API 获取完整的 A 股日线数据 - **Schema-on-API**：根据 API 响应动态创建和扩展表结构 - **数据质量检查**：内置多层数据质量验证机制 - **Airflow 编排**：支持自动化日更和历史回填 - **ClickHouse 存储**：高性能列式数据库存储时间序列数据
Our value and principle is developer success. We truly care about helping developers achieve their goals — not just shipping features, but ensuring every developer who uses Hive can build, debug, deploy, and iterate on agents that work in production. Developer success means our developers succeed in their own work: automating real business processes, shipping products, and growing their capabilities. If our developers aren't winning, we aren't winning.
Step 3 - Design Artifacts. Generates architecture diagrams and Architecture Decision Records (ADRs) for Azure infrastructure. Uses azure-diagrams skill for visual documentation and azure-adr skill for formal decision records. Optional step - users can skip to Implementation Planning.
Step 3 - Design Artifacts. Generates architecture diagrams and Architecture Decision Records (ADRs) for Azure infrastructure. Uses azure-diagrams skill for visual documentation and azure-adr skill for formal decision records. Optional step - users can skip to Implementation Planning.
| Source | Contribution | |--------|--------------| | [Skill Authoring Best Practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices) | Core principles, progressive disclosure, evaluation patterns, anti-patterns | | [Skills Overview](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview) | Skill structure, runtime environment, how skills work | | [Claude Code Skills Documentation](https://code.claude.com/docs/en/skills) | Skill loading
PocketPaw's memory system provides long-term fact storage, session history with smart compaction, and a user profile loaded into every conversation.
This file tracks MicroSims that need screenshots captured. Last updated: 2026-02-14
Failing to hold a queue freeze during teardown or reconfiguration allows bios to complete concurrently, causing use-after-free on queue state, stale elevator data, or torn reads of `q->nr_requests`.
> Comprehensive reference for Service Level Agreements, Objectives, and Indicators. > Designed for incident commanders who must understand, protect, and communicate SLA status during and after incidents. ---
**Type**: Evaluative **Executor**: LLM **Knowledge**: Security Principles (ZT, SOD, LP), security-design.yaml ---
**Type**: Evaluative **Executor**: LLM **Knowledge**: Security Principles (ZT, SOD, LP), security-design.yaml ---
**Type**: Evaluative **Executor**: LLM **Knowledge**: Security Principles (ZT, SOD, LP), security-design.yaml ---
Using the wrong lock type for the execution context causes deadlocks (sleeping in atomic context), missed wakeups, or priority inversion. The table below shows which lock types provide correct protection for data shared across the listed contexts.
Using the wrong lock type for the execution context causes deadlocks (sleeping in atomic context), missed wakeups, or priority inversion. The table below shows which lock types provide correct protection for data shared across the listed contexts.
Sync current branch with main/master (fetch, rebase or merge)
Generates Step 7 as-built documentation suite after successful deployment. Reads all prior artifacts (Steps 1-6) and deployed resource state to produce comprehensive workload documentation: design document, operations runbook, cost estimate, compliance matrix, backup/DR plan, resource inventory, and documentation index.
Incorrect locking of runqueues causes deadlocks, data corruption in the RB-tree, and use-after-free of task structs when concurrent CPUs observe inconsistent state.
- Runqueue locks are `raw_spinlock_t` (never sleeps, even on PREEMPT_RT) - Multi-runqueue operations must lock in consistent order to prevent deadlock - `double_rq_lock()` / `double_rq_unlock()` handle ordering automatically (swaps to ascending order internally via `rq_order_less()`) - `lockdep_assert_rq_held()` validates rq lock is held in accessors - `task_rq(p)` expands to `cpu_rq(task_cpu(p))`. Without pinning or holding `pi_lock` / rq lock, the task can migrate after `task_cpu(p)` is re
```bash vllm-mlx-bench --model mlx-community/Qwen3-VL-8B-Instruct-4bit --video
Desired state for every machine running an OpenClaw gateway. Each section describes **what correct looks like**, how to **verify** it, and how to **fix** drift. **How to use this document:** 1. Read each section's desired state 2. Check actual state using the verification commands 3. If actual matches desired: move on 4. If actual differs: apply the fix, then re-verify 5. Items marked **MANUAL** require human intervention (sudo, login, GUI) — flag these and stop **See also:** `health-check.md...
Baseline configuration for every machine running an OpenClaw gateway. The health check agent can verify these settings; fleet management uses this as the source of truth for what "correctly configured" means.
基于现有插件的表依赖关系，创建一组**预定义的插件组合**，覆盖常见的数据同步场景（如"A股完整数据"、"财务报表完整同步"、"指数数据完整同步"等），用户可直接使用这些组合进行一键同步，无需手动配置。
当前系统缺少ETF（交易型开放式指数基金）相关的数据获取插件，无法支持： 1. **ETF基础信息**：无法获取国内ETF的基础信息（代码、名称、管理人、跟踪指数等） 2. **ETF日线行情**：无法获取ETF每日收盘后的OHLCV数据 3. **ETF复权因子**：无法获取ETF的复权因子，影响价格调整计算 4. **ETF分钟数据**：无法获取ETF的分钟级别行情数据
Our value and principle is developer success. We truly care about helping developers achieve their goals — not just shipping features, but ensuring every developer who uses Hive can build, debug, deploy, and iterate on agents that work in production. Developer success means our developers succeed in their own work: automating real business processes, shipping products, and growing their capabilities. If our developers aren't winning, we aren't winning.
- [x] 创建 `src/stock_datasource/config/` 目录 - [x] 将 `modules/datamanage/trade_calendar.csv` 复制到 `config/trade_calendar.csv` - [x] 创建 `src/stock_datasource/core/trade_calendar.py` - 实现 `TradeCalendarService` 单例类 - 实现 `get_trading_days(n, end_date)` 方法 - 实现 `is_trading_day(date)` 方法 - 实现 `get_prev_trading_day(date)` 方法 - 实现 `get_next_trading_day(date)` 方法 - 实现 `get_trading_days_between(start, end)` 方法 - 实现 `refresh_calendar()` 方法（从 TuShare 更新）
- [x] 1. 确认 api.py 无外部依赖 - 搜索所有对 `portfolio/api.py` 的引用 ✅ 无后端依赖 - 检查是否有测试文件依赖 ✅ 无 - 前端引用的是 `frontend/src/api/portfolio.ts`，不是后端文件 - [x] 2. 删除废弃的 api.py 文件 - 删除 `/modules/portfolio/api.py` ✅ - 验证服务正常启动 ✅ 模块导入正常 - [x] 3. 验证用户隔离功能 - pytest 未安装，跳过自动化测试 - 代码审查确认 `router.py` 的所有接口都使用 `Depends(get_current_user)`
本文档列出实现港股财务数据插件的具体任务清单。