Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
talent-factory
GitHub 제작자 프로필

talent-factory

2개 GitHub 저장소에서 수집된 37개 skills를 저장소 단위로 보여줍니다.

수집된 skills
37
저장소
2
업데이트
2026-06-25
저장소 탐색

저장소와 대표 skills

dev-browser
소프트웨어 개발자

Browser automation with a persistent session, driven by the Playwright Python API. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.

2026-06-25
ponytail-audit
소프트웨어 품질 보증 분석가·테스터

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/core:ponytail-audit". One-shot report, does not apply fixes.

2026-06-25
ponytail-debt
소프트웨어 품질 보증 분석가·테스터

Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/core:ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.

2026-06-25
ponytail-review
소프트웨어 품질 보증 분석가·테스터

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /core:ponytail-review. Complements correctness-focused review, this one only hunts complexity.

2026-06-25
ponytail
소프트웨어 개발자

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.

2026-06-25
wiki-ingest
데스크톱 출판 전문가

Ingests a new source (web clipping, AI chat export, raw note, transcript) into an Obsidian-based LLM knowledge wiki. Files the source under _raw/, distills it into one or more _wiki/ pages, updates index and log, and pulls bidirectional cross-references. Triggers when the user asks to "ingest this source", "digest this clipping into the wiki", or runs /wiki:ingest while working in a configured wiki vault.

2026-06-22
wiki-lint
데스크톱 출판 전문가

Runs a structural and content health check on an Obsidian-based LLM knowledge wiki. Detects frontmatter issues, broken or asymmetric cross-references, contradictions, stale claims, tag discipline violations, migration backlog overflow, missing hub pages, and orphan content. Produces a structured lint report. Triggers when the user runs /wiki:lint, asks for a "wiki health check", or asks to lint the knowledge wiki.

2026-06-22
wiki-maintain
데스크톱 출판 전문가

Runs non-interactive maintenance on an Obsidian-based LLM knowledge wiki — deterministic validation, semantic health checks, trivial auto-fixes, and a written report. Built to be scheduled (cron/launchd). Triggers when the user runs /wiki:maintain, asks to "run wiki maintenance", or "auto-fix the wiki".

2026-06-22
이 저장소에서 수집된 skills 34개 중 상위 8개를 표시합니다.
저장소 2개 중 2개 표시
모든 저장소를 표시했습니다