프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. Google로 로그인하면 리뷰를 쓸 수 있어요.프로토타입 · 30분마다 업데이트
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

FDEOps Skill

저장소 ↗

제작자: suboss87★ 818 (whole repo)skill 36개

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 36 skills

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category 코딩
Maker’s original description
Forward deployed engineering skills for AI coding agents.
제작자용: README에 배지 달기

제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/suboss87-fdeops.svg)](https://mcp.popnx.com/en/skills/suboss87-fdeops)

함께 쓰기

같은 작업에서 AI를 서비스에 연결하는 MCP

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

제작자: morluto널리 사용됨↓ 38.9만/주★ 46.4만6일 전 업데이트

MCP · 서비스 연결내 컴퓨터에서 실행

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

제작자: fallow-rs널리 사용됨↓ 244.1만/주★ 5.4천어제 업데이트

MCP · 서비스 연결내 컴퓨터에서 실행

Desktop Commander

MCP server for terminal commands, file operations, and process management

제작자: wonderwhy-er널리 사용됨↓ 74만/주★ 1만6일 전 업데이트

MCP · 서비스 연결내 컴퓨터에서 실행

비슷한 Skill

같은 종류의 작업, Skill 목록과 같은 순서

비슷한 항목과 비교
이 항목
FDEOps
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
제작자suboss87morlutomultica-aiGraphify-Labsharry0703
Skill 수361111
GitHub 별818465,460233,910149,364144,149
마지막 코드 변경2026년 11월 11일2026년 11월 17일2026년 4월 20일2026년 11월 17일2026년 11월 17일
라이선스MITMIT–Apache-2.0MIT

suboss87의 Skill(지시 묶음) 36개, AI가 읽고 그대로 일해요 · MCP server가 아니에요

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

This set has 36 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below

Showing 30 of 36 See all on GitHub

  • audit

    Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.

  • board-memo

    Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.

  • brief

    Clarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.

  • build

    Implement a scoped software change for a customer and verify its behavior. Use for delivery work with an understood outcome, not incident response.

  • business-case

    Develop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.

  • connect

    Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host.

  • dashboard

    Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.

  • debrief

    Turn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.

  • debug

    Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.

  • demo-prep

    Prepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.

  • discover

    Trace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.

  • earn-trust

    Plan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.

  • evaluate

    Evaluate an AI workflow against representative cases and its permitted actions. Use for model, retrieval or agent evaluation; tests do not grant release authority.

  • fde

    Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. U…

  • feedback

    Assess a field lesson for reuse or product feedback without exposing customer context. Use for recurring deployment lessons; distinguish a hypothesis from a validated pattern.

  • handoff

    Transfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.

  • ingest

    Fetch requested source material and prepare sourced engagement updates. Use to catch up from external notes or messages; applying updates requires a bound record and confirmation.

  • integrate

    Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.

  • options

    Compare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.

  • plan

    Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.

  • poc

    Run a bounded customer proof of concept to test a consequential uncertainty. Use for a spike or pilot with a question and decision deadline, not a full rollout.

  • prioritize

    Choose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals.

  • qa

    Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.

  • readout

    Prepare a sponsor update separating promised outcomes, measured results and customer acceptance. Use for progress readouts or defending a delivery claim.

  • red-team

    Stress-test a plan, brief or delivery claim against evidence and plausible failure modes. Use when the user asks for a red team or preparation for a consequential decision.

  • rescue

    Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.

  • review

    Review a proposed customer code change against its intended outcome and operational risks. Use for a diff or PR review; report evidence and actionable findings.

  • rollback

    Prepare and rehearse a recovery path for an intended release. Use when rollback is assumed, untested or previously failed; follow the environment authority for any drill.

  • runbook

    Write an operating runbook from the delivered system and verified procedures. Use when the customer team or a successor needs to operate without the original engineer.

  • scope

    Assess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.

Skill과 MCP의 차이

MCP = 손

AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.

Skill = 안내서

작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.

겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.

쓸 수 있는 앱

제작자가 밝히지 않음 · SKILL.md 형식 Skill은 Claude Code, Codex, Cursor 같은 Agent Skills 지원 앱에서 써요

설치

Pick a skill first

This repo has 36 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

The maker’s command installs the whole set of 36
Node.js 설치 (아직 없다면)

이미 설치했나요? 먼저 확인 · 터미널을 열고 이 명령을 입력한 뒤 Enter

node -v
  • 버전 번호(예: v26.13.1)가 나오면 설치된 것입니다. 이 단계는 건너뛰세요
  • "command not found"(Windows는 "is not recognized")가 나오면 아직 설치하지 않았거나, 방금 설치해서 터미널을 닫았다가 다시 열어야 합니다
터미널 여는 법

Mac: ⌘ + Space를 누르고 Terminal 입력 후 Enter

Windows: 시작 메뉴를 열고 Windows PowerShell 입력 후 "열기"

아직 설치하지 않았다면: 공식 다운로드 페이지에서 LTS 버전과 클릭형 설치 파일을 고르세요: Mac은 .pkg · Windows는 .msi. 더블클릭 후 끝까지 진행하면 됩니다. curl 명령은 필요 없습니다

Node.js 다운로드 페이지 열기 ↗

설치가 끝나면 터미널을 닫았다가 다시 열고 같은 명령을 실행하세요. 버전 번호가 나와야 합니다: node -v

한 번 설치하면 Node.js가 필요한 모든 도구에서 쓸 수 있습니다

명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요

제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요

토론

질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.

아직 글이 없어요. 처음으로 질문하거나 공유해 보세요.

이곳의 글은 사용자가 쓴 것으로, PopNx 팀의 글이 아니에요.

로그인하고 글쓰기

GitHub 정보

GitHub 스타
818
Stars are for the whole repo, not each skill
제작자
suboss87
라이선스
MIT
최근 코드 수정
2026년 11월 11일
repo 안 SKILL.md(번역본과 템플릿 포함)
30
토픽
ai-agents, claude, claude-skills, codex, codex-skill, cursor, fde, forward-deployed-engineering