839건 · 관련도순
Review unresolved GitHub pull request comments against the current code, apply minimal fixes for valid issues, and reply to review threads. Comments that need human judgment remain open, while fixed or unnecessary requests are resolved with explanations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research technology and advanced manufacturing investments by tracing supply chain bottlenecks, or inputs that are hard to expand. Compare companies using dated evidence, potential earnings contributions, and conditions that would change their research priority.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check package changes against changesets, the files describing release updates, to assess summaries and required version increases. Use it to review pull requests or uncommitted changes and obtain a structured verdict with errors, warnings, and the required bump.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide an agent to ground judgments in evidence, separate facts from inferences and unknowns, verify results, and diagnose failures. It also selects a suitable methodology skill when investigation, prioritization, validation, or another structured approach would help.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate firsthand sources before making a judgment or recommendation. Separate verified facts, reasoned inferences, and unknowns, document their sources, and produce a conclusion that explains the current situation, constraints, and remaining uncertainty.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Combine feedback from users, code, logs, and runtime results into a reasoned plan. Separate agreement from conflicting evidence, explain the judgment, and validate it with the people or systems that supplied the original information.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare research records you provide to see changes in facts, scores and judgments. Use when the user asks to investment review with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find connections between notes and update MOCs. Requires semantic judgment to identify genuine relationships. Use after /reduce creates notes, when exploring connections, or when a topic needs synthesis. Triggers on "/reflect", "/reflect [note]", "find connections", "update MOCs", "connect these notes".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply Hunt and Thomas-inspired pragmatic programming rules when improving engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, or adaptability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Score one blog post (or a folder of posts) on a 5-category 100-point scale covering content quality, SEO, E-E-A-T, technical elements, and AI citation readiness. Runs the deterministic analyzer first, then adds judgment and prioritized Critical/High/Medium/Low fixes. Advisory style diagnostics never infer authorship or affect the score. Exports markdown, JSON or table; works with MDX, markdown, HTML or a URL. Use when the user asks to analyze, score, rate or check the quality of specific posts ("analyze blog", "blog score", "check blog quality", "rate this post"). For a site-wide health check (orphan pages, cannibalization, stale content, schema across all posts) use blog-audit instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assesses whether study results are trustworthy by auditing design integrity, sample structure, statistical handling, bias control, validation chain, and claim discipline. It identifies where results are robust, fragile, overfit, under-validated, or overclaimed. Always separate reported findings from reliability judgment. Never fabricate references, PMIDs, DOIs, trial identifiers, study features, or validation claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A medical-research-native literature reading skill for users with clinical, bioinformatics, translational, and basic experimental backgrounds. Use this skill whenever a user wants to read, analyze, critique, or interpret a medical or scientific paper — whether they provide a PDF, abstract, DOI, PMID, or just a title. Triggers include requests like \"analyze this paper\", \"critique this study\", \"is this a strong paper?\", \"give me similar studies\", \"prepare me for journal club\", \"help me understand this bioinformatics paper\", \"what are the weaknesses here?\", or \"turn this into a mind map\". Also activate for any downstream deliverables such as journal club kits, comparison tables, PI decision briefs, replication starters, or follow-up experiment designs. Do NOT treat as a generic summarizer — this skill performs structured evidence-type classification, track-specific critical appraisal, interpretation-boundary judgment, and research-grade follow-up generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when evaluating a business through Buffett-style ownership, owner earnings, durable moat, management quality, capital allocation, and margin-of-safety judgment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when evaluating a decision through Charlie Munger-style mental models: inversion, incentives, quality filters, multidisciplinary reasoning, and concentrated judgment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitor_only, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Monitor current news and reaction signals, then decide which are credible newsjacking opportunities for a client. Uses the local monitoring engine for evidence, but the skill owns PR judgment, brand safety, standing, decay, angle fit, and handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to run/interpret `hephaestus security scan`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces the reader-facing HTML artifact — report, dashboard, architecture view, data browser, or review workbench — evidence-backed, browser-verified. Use when the deliverable IS a visual HTML report, or the user asks for an HTML/web presentation. Load data-visualization-discipline for chart judgment. Not for chat status or Markdown prose unless asked to become a report; not for PowerPoint (deck-creator Route C).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a real brainstorm — divergent generation without judgment, then convergent selection with explicit criteria — instead of listing ten obvious ideas and calling it creativity. Use when asked to brainstorm, generate ideas or options, explore a solution space, or name something. Produces a genuinely wide option set (including the weird tail), then a shortlist selected against named criteria with the rejects preserved.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manual intent elicitation skill. Use when the user asks to clarify a fuzzy idea, run an elicitation session, design an agent/skill/workflow, identify strategic tension, do a postmortem, align taste/brand direction, or turn vague judgment into an actionable Intent Brief. The skill asks 3–5 sharp questions first, then compiles answers into an Intent Brief and routes the result into system/workflow change. Never run automatically or on a schedule.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer work, or when the user invokes $add. Over-register freely; the developer drops with "drop A", "drop A,C", or "drop all".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explicit landing-page build and deploy operator. Loads marketing and frontend judgment, scaffolds the smallest suitable site, verifies it rendered, deploys to the configured target.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Power BI report design canon covering design identity, visual hierarchy and the 3-30-300 rule, layout/spacing/alignment, color discipline, chart selection, KPI and card design, tables and matrices, accessibility, and the closing design gate. The shared reference home for report design judgment, routed to by the create-pbi-report, pbir-cli, review-report, modifying-theme-json, and custom-visual skills. Load when committing a design identity or making a design, layout, color, chart-selection, or accessibility decision for a report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.