104건 · 관련도순
Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Examine beliefs tied to personal labels and rethink habits that resist change. The skill guides reflection, acknowledgment of avoided facts, and a new self-image supported by commitments to others and small daily actions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan and verify OpenRig startup, shutdown, and recovery. Compare reported status with actual running sessions, distinguish recovery outcomes, and define reboot tests that expose partial failures instead of hiding them behind a fresh launch.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check files created or edited by another agent, subprocess, or tool against explicit requirements. Verify the actual location, structure, counts, and key fields, then rerun with absolute paths when the results contradict the completion report.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze git history to map contributors to security-sensitive files and identify ownership gaps. Estimate bus factor, a measure of dependence on few people, group files that change together, and export CSV or JSON for further analysis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess Microsoft 365 and Entra ID authentication using tenant discovery, login error analysis, and browser-based verification. It provides attempt tracking and evidence templates to distinguish credential results from access-policy restrictions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
XML sitemap audit — find and fix the sitemap problems that quietly waste crawl budget and slow indexing. Discovers the sitemap (robots.txt, /sitemap.xml, sitemap index), validates structure and size limits, and cross-checks the URLs it lists against reality: non-200 / redirected / noindex / canonicalized-away URLs that shouldn't be in a sitemap, plus indexable pages that are missing from it. Reviews lastmod accuracy, sitemap-index organization, and robots.txt reference. Use this skill whenever the user asks about sitemaps, sitemap errors in Search Console, "sitemap couldn't fetch / has errors", crawl budget, pages not getting indexed, or whether their sitemap is clean. Trigger on: "sitemap", "sitemap.xml", "XML sitemap", "sitemap errors", "sitemap audit", "couldn't fetch sitemap", "crawl budget", "pages not indexed sitemap", "sitemap index", "lastmod", "robots.txt sitemap", or any sitemap/crawl-coverage question. For a full-site SEO audit use /seo-analysis; for broken links use /broken-link-checker.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "pick which social channels to run", "should we be on X platform or 小红书", or "plan our organic social channel portfolio"; produces an audience/objective-first portfolio with capability/access matrix, cadence-budget reality check, declared ECHO operating profile, boundary routing, and proposed-state registry events. Not for recording canonical channel facts — use channel-registry. 社媒渠道选择/渠道组合规划/平台能力矩阵/自然社媒
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a fast, honest competitive scan — the dimension table built from public evidence (sites, docs, pricing pages, changelogs, reviews), the claims-vs-observed discipline, and the so-what synthesis that ends in moves, not a landscape mural. Use when asked what are competitors doing, quick scan of these three rivals, how does our pricing/feature set compare, or prep the competitive slide honestly. Produces the evidence-based comparison table, the marketing-vs-reality flags, the so-what synthesis, and the staleness date.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compute what a degree will actually cost — sticker minus real aid, inflated per year, split into cash and loans, with the loan's decade-long monthly tail made visible before enrollment instead of after. Use when asked what will college really cost, compare these two offers' real prices, how much loan payment after graduation, or is this school affordable. Produces the all-in number from the script, the offer-letter decode (grants vs loans untangled), the monthly-tail reality check, and the two-school comparison.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a realistic plan to change careers — mapping your transferable skills, the real gaps, and a bridge that doesn't require torching your income overnight. Use when asked to help me change careers, career pivot plan, how do I switch to [field], or I want a new career but don't know how. Produces a transferable-skills map, an honest gap analysis to the target role, a staged bridge (skill-building, positioning, side-door entry), a financial-runway reality check, and a narrative that reframes your background as an asset — not a starting-from-zero story.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a realistic personal monthly budget from someone's income and expenses. Use when asked to make a budget, plan monthly spending, allocate income, or get finances under control. Produces a categorized budget (a 50/30/20-style allocation tuned to their reality), a surplus/shortfall number, and concrete next moves. Educational, not regulated financial advice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit claims that work is done or shipped against the diff or repo. Use when: asked whether something really got done, even if it looks obvious.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extracts, filters, annotates, and exports differential expression results from DESeq2 or edgeR with proper handling of padj=NA (independent filtering, Cook's outliers, all-zero), multiple-testing correction choice (BH vs Storey q-value vs IHW vs lfsr), TREAT vs post-hoc fold-change filtering, p-value histogram diagnostics, gene annotation via org.db/biomaRt/mygene, GSEA preranked input, ORA background construction, replication reality (Schurch 2016 small-n result), and SABV/sex-stratified reporting. Use when extracting and interpreting DE results, troubleshooting padj=NA, choosing FDR method, preparing ranked lists for pathway analysis, annotating gene IDs, or comparing DESeq2 vs edgeR outputs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building ANY 2D or 3D game with SpriteKit, SceneKit, or RealityKit, or adding touch controls or game controller support. Covers scene graphs, ECS, physics, actions, game loops, rendering, TouchController, GCController.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain and extend existing SceneKit 3D scenes and visualizations. Use when working with SCNView, SCNScene, SCNNode scene graphs, SceneKit geometry/materials/lights/cameras, SCNAction animation, SCNPhysicsBody physics, SCNParticleSystem effects, .scn/.dae/.abc SceneKit assets, shader modifiers, or SwiftUI SceneView. SceneKit is soft-deprecated and in maintenance mode; route new apps, significant updates, USD/USDZ pipelines, and migration planning toward RealityKit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds multiplayer spatial board games using TabletopKit on visionOS. Use when creating tabletop game experiences with boards, pieces, cards, or dice; managing seats, turns, equipment state, TabletopAction flows, or TabletopInteraction delegates; synchronizing gameplay through FaceTime Group Activities; rendering with RealityKit; or implementing snapping, tosses, and physics on a virtual table surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a business plan from the perspective of the solo founder who has to actually execute it. Asks the brutal operational questions: Can I build this with my time budget? Can I keep it running? Will my cashflow survive? Outputs a verdict — SHIPPABLE NOW / SHIPPABLE WITH DESCOPE / NEEDS HIRE / WRONG STACK. Use when a plan looks great on paper and you want to know whether a solo operator can actually execute it. Triggered by: 'operator review', 'can I actually do this solo', 'execution reality check', '操盘视角', '我能不能干得动'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build. Use it whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. It has three on-ramps: the full journey, a validate-only pass ("is my idea worth building", "reality-check this idea"), and a plan-only path for someone arriving with validation done ("I already validated my idea", "I have the research, just plan my MVP", "skip the research"). ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a sized Instagram hashtag set for a post using the 2026 reality that 3 to 5 well-chosen tags beat 30 random ones. Sizes each tag as niche (under 50k posts), mid (50k to 500k), or broad (500k+), then assembles a 2-3 niche, 1-2 mid, 0-1 broad mix that a small or mid account can actually rank in, matched to the post content and rotated to avoid spam patterns. Use to choose hashtags for a caption, carousel, or Reel. Not for writing the caption itself (use ig-caption-writer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the root cause of a problem before proposing a fix. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit claims that work is done or shipped against the diff or repo. Use when: asked whether something really got done, even if it looks obvious.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.