152 skills · sorted by relevance
Refresh drift-prone documentation against current code. Reads docs/architecture/freshness-catalog.yml, diffs against the last sweep's upstream/main anchor, regenerates mechanical entries, processes editorial markers, and opens one PR per sweep with a report file.
The English summary is being prepared. Showing the original description.
Search a local Notion archive, inspect databases, count pages with read-only SQL, and refresh Markdown exports when needed. Check synchronization status to understand how current the stored information is and identify known gaps.
Research current facts, compare options, or investigate people and companies using public sources and supplied context. This skill selects an appropriate research workflow and separates evidence, inference, and recommendations, including dates where freshness matters.
Repeat candidate searches and comparisons while keeping an append-only decision log. Record evidence, compare results with earlier winners, and check replay, freshness, and approval requirements before moving to live trading or production actions.
Find bottlenecks in large data transfers, imports, transformations, and historical data catch-up. Benchmark alternative processing methods, turn the fastest correct approach into a repeatable workflow, and verify file counts, row counts, and timestamps after execution.
Browse World Monitor's curated news feeds by topic or language, with duplicate stories removed. Review headlines, sources, publication dates, threat labels, and alert flags, then summarize selected headlines or translate them through the connected tools.
Create and update dashboards with charts, metrics, and tables drawn from connected data sources or attached files. Link displayed values to their sources so readers can inspect queries, calculations, and freshness while reviewing business indicators or recurring reports.
Explore unfamiliar code with GitNexus to understand project structure and execution flows. Find related functions, inspect their callers and callees, and read implementation files to explain how a feature works, with repository and index freshness information.
Find the right GitNexus tools and workflows for exploring code relationships. This reference explains available commands, graph queries, and resources, including how to check which branch an answer describes and whether its index is current.
Build data quality checks with Great Expectations, dbt tests, and data contracts, which define shared expectations between teams. Check missing values, duplicates, and freshness, then integrate validation into data pipelines and CI/CD.
Explore unfamiliar code with Codebase Memory to map architecture, trace function calls and dependencies, and assess change impact. Findings are checked against source files, with index freshness and coverage considered before drawing conclusions.
Browse registered trading strategies and compare evidence from backtests, which simulate trades on historical data. Filter by market conditions, trade counts, risk-adjusted returns, and cost feasibility, inspect evidence age, and rebuild the evidence cache from local runs.
Build Splunk pipelines that import threat intelligence and match security events against indicators such as malicious IP addresses, domains, and file hashes. Add source, confidence, and severity details so analysts have context when investigating matches.
Investigate slow jobs, stale data, and timeout alerts by timing the specific operation and comparing monitoring thresholds. Produce an evidence-based verdict that distinguishes insufficient time, stalled work, and false alerts before proposing changes.
Compare saved knowledge with current web sources using Perplexity. This skill produces a cited research page that separates new developments, supporting evidence, and contradictions, with suggested updates to stored information about people, companies, or deals.
Review logs and source files from a completed manual example run. Check that results are current and complete, verify intended behavior beyond successful exit codes, and distinguish product defects from environment or credential problems.
Design research agents that search, read, and turn web or internal sources into clear reports. The playbook defines source freshness, citations, search limits, and a consistent format that separates findings from information the agent could not verify.
Design systems that collect, transform, and store data. Choose between scheduled and continuous processing, generate workflow configurations, validate data quality, and analyze performance using guidance for tools including Python, SQL, Spark, Airflow, dbt, and Kafka.
Write, revise, and review beads user documentation using consistent terminology, explanations, diagrams, and navigation. Follow project rules for generated pages and release alignment, with checks for links, freshness, and documentation consistency.
Monitor a data warehouse for stale tables, unusual row counts, column changes, and failed loads. Receive alerts with evidence and likely causes, plus GitHub issues for human review, while warehouse data remains unchanged.
Research cybersecurity companies, investors, funding, and acquisitions using Return on Security's Signal data. Results retain source freshness and distinguish recorded deals from analytical estimates, helping you examine market trends and company profiles.
Maintain LangBot skill assets by organizing operating rules, reference guides, test cases, fixtures, and troubleshooting entries. Check existing material before adding files, keep detailed instructions in one place, and verify that indexes stay current.
Review website content for AI citation readiness using E-E-A-T: experience, expertise, authoritativeness, and trustworthiness. Assess evidence, author information, structure, freshness, and topic coverage, then receive scores, passage-level findings, and specific recommendations for improvement.
Build and search a project knowledge graph, a map of information and its relationships. Check matching entries, relationship confidence, graph freshness, and changes since the previous build to understand the project's recorded structure.