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

likesjx

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

수집된 skills
34
저장소
4
업데이트
2026-06-22
저장소 탐색

저장소와 대표 skills

mcp-surface-hygiene
기타 컴퓨터 관련 직업

Use this skill when reviewing, provisioning, or documenting MCP membrane tools for external clients such as Perplexity, Claude, or Codex. It keeps Muninn capture, LifeGraph tools, and raw graph/runtime tools separated.

2026-06-22
role-authoring
기타 컴퓨터 관련 직업

Use this skill when authoring or revising an agent role lens before governed execution. It gathers the missing role definition inputs, explains the required payload shape, and prepares the payload for the role.create_or_update workflow.

2026-06-14
philotic-muninn-memory-habit
기타 컴퓨터 관련 직업

Use at session start and closeout to retrieve and write durable Muninn continuity context.

2026-06-08
philotic-planning
기타 컴퓨터 관련 직업

Use when the user needs planning, decomposition, orchestration, or seam selection guidance.

2026-06-08
philotic-verification
소프트웨어 품질 보증 분석가·테스터

Use when the user needs validation strategy, test selection, or confidence reporting.

2026-06-08
lifegraph-truth-summarizer
기타 컴퓨터 관련 직업

Use this skill when an agent summarizes the operator's LifeGraph, answers "what is in my LifeGraph?", or turns LifeGraph records into planning context. It requires provenance-aware summaries that separate confirmed graph facts from seeded placeholders, inferred intent, and recommended next structure.

2026-06-07
cron-manage
기타 컴퓨터 관련 직업

Create, inspect, enable, disable, and remove scheduled cron jobs on the hotel. Use when the operator or an autonomous workflow needs recurring work at a fixed schedule.

2026-06-04
muninn-memory-protocol
소프트웨어 개발자

Use this skill when a client should adopt the shared Muninn memory workflow for continuity across sessions. Trigger when setting up Muninn-backed recall/write-back habits, wiring a client to the shared helper, or standardizing memory behavior across multiple cognitive clients.

2026-05-18
이 저장소에서 수집된 skills 23개 중 상위 8개를 표시합니다.
engine-check
소프트웨어 개발자

Use this skill to validate repo health before starting work. It checks that required files, tools, and services are present and functional. Run at session start or after major structural changes.

2026-03-15
runtime-debugger
소프트웨어 개발자

Use this skill when debugging live runtime behavior in a multi-process or distributed system, especially IPC framing, socket registration, supervised process startup, routing/materialization, liveness, or request/response mismatches. Trigger when the user asks to watch a live stack, debug runtime integration issues, inspect process/socket state, or compare test behavior against real execution. This skill is general and should not assume a Rust-only stack.

2026-03-15
architecture-docs-maintainer
소프트웨어 개발자

HIGH PRIORITY. Use this skill when changing architecture or workflow docs so domain, frontmatter, status truth, proposal links, and task links stay aligned automatically. Trigger for edits in docs/architecture/, docs/README.md, or docs/task.md when the work changes current truth, near-future seams, proposal status, or documentation structure.

2026-03-15
proposal-maintainer
프로젝트 관리 전문가

HIGH PRIORITY. Use this skill to keep architecture and process proposals concise, current, and linked to active tasks. A proposal is not a static doc; it is an active plan. Trigger for disposition updates, task alignment, or removing stale certainty. Pair this with architecture-docs-maintainer when metadata, domains, or source-of-truth linkage also need upkeep.

2026-03-15
muninn-memory-habit
소프트웨어 개발자

HIGH PRIORITY. Use this skill at the START of EVERY session to retrieve project context and during the session to store decisions. It is the mandatory bootstrap mechanism for continuity and the engine for project optimization. Retrieve before meaningful work, write back important decisions, and use revealed gaps to improve repo-local protocols.

2026-03-15
verification-ladder
소프트웨어 품질 보증 분석가·테스터

Use this skill when deciding how deeply to validate a change or when explaining confidence in a code change. Trigger for test planning, selecting the right validation rung, or classifying confidence as test-green, smoke-green, or watched-live-green. Do not use this skill for runtime root-cause investigation or slice close-out unless validation choice is the main task.

2026-03-15
slice-closeout
소프트웨어 개발자

HIGH PRIORITY. Use this skill to finish every implementation slice. It mandates "green status clearing" (verified build/test/smokes), updates to docs/task.md, and explicit disposition updates for touched architecture proposals. No slice is complete until this operational close-out is recorded and committed.

2026-03-15
your-skill-name
소프트웨어 개발자

One-paragraph description of when to use this skill, what triggers it, and what it should NOT be used for.

2026-03-14
저장소 4개 중 4개 표시
모든 저장소를 표시했습니다