How do I install the [object Object] skill?

Run npx skillmds@latest add ydnikolaev/object-object in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the [object Object] skill do?

[object Object] It is listed under AI & ML on SkillMD.

Is [object Object] safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with [object Object]?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is [object Object] free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published [object Object]?

ydnikolaev (@ydnikolaev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

[object Object] by ydnikolaev — Agent Skill

Name: [object Object]
Author: ydnikolaev

File contents

[!IMPORTANT]

First Step: Read Project Config & MCP

Before making technical decisions, always check:

File Purpose

project/CONFIG.yaml Stack versions, modules, architecture

mcp.yaml Project MCP server config

mcp/ Project-specific MCP tools/resources

Use project MCP server (named after project, e.g. mcp_xlinefitness-bot_*):

list_resources → see available project data

*_tools → project-specific actions (db, cache, jobs, etc.)

Use mcp_context7 for library docs:

Check mcp.yaml → context7.default_libraries for pre-configured libs

Example: libraryId: /nuxt/nuxt, query: "Nuxt 4 composables"

File	Purpose
`project/CONFIG.yaml`	Stack versions, modules, architecture
`mcp.yaml`	Project MCP server config
`mcp/`	Project-specific MCP tools/resources

When to use this skill

Trigger 1: Description of situation...
Trigger 2: Description of situation...
Anti-pattern: Do NOT use this skill when...

Decision Tree

Before acting, determine the specific scenario:

IF [Condition A]:
- Use scripts/script_a.py
- Refer to references/guide_a.md
IF [Condition B]:
- Follow the manual workflow below
ELSE:
- Ask user for clarification

Workflow

Phase 1: Preparation

Verify prerequisites...
Check for existing files...

Phase 2: Execution

Tip: Use task_boundary to track progress if this is a long task.

Step 1...
Step 2...

Phase 3: Verification

Run validation checks...
Notify user...

Iteration Protocol (Ephemeral → Persistent)

[!IMPORTANT] Phase 1: Draft in Brain

Create drafts as UI Artifacts (in brain/ conversation directory)

Iterate with user via notify_user until approved

Keep Q&A and sketches here — do NOT pollute project/docs/

Phase 2: Persist on Approval

ONLY after "Looks good" → write final to project/docs/ path

Update file status: Draft → Approved in header

The project/docs/ folder is the ONLY memory that survives sessions

Artifact Ownership

Creates: project/docs/<category>/<artifact>.md
Reads: <previous skill artifacts>
Updates: project/docs/ARTIFACT_REGISTRY.md (status + timestamp)

TDD Protocol

[!CAUTION] NO CODE WITHOUT FAILING TEST.

Red: Write test → Fail.

Green: Write code → Pass.

Refactor: Clean up. NEVER write implementation code without a failing test. NEVER fix a bug without a reproduction case.

Handoff Protocol

[!CAUTION] BEFORE delegating to next skill:

✅ Final document exists in project/docs/ (not just brain artifact)

✅ File header changed from Draft to Approved

✅ project/docs/ARTIFACT_REGISTRY.md updated to ✅ Done

✅ User approved via notify_user

THEN delegate

Resources

scripts/:
- example_script.py: {{SCRIPT_DESC}}
references/:
- reference.md: {{REF_DESC}}

---name: object-objectdescription: [object Object]---# {{SKILL_TITLE}}{{SKILL_PURPOSE_SUMMARY}}> [!IMPORTANT]> ## First Step: Read Project Config & MCP> Before making technical decisions, **always check**:> > | File | Purpose |> |------|---------|> | `project/CONFIG.yaml` | Stack versions, modules, architecture |> | `mcp.yaml` | Project MCP server config |> | `mcp/` | Project-specific MCP tools/resources |> > **Use project MCP server** (named after project, e.g. `mcp_xlinefitness-bot_*`):> - `list_resources` → see available project data> - `*_tools` → project-specific actions (db, cache, jobs, etc.)> > **Use `mcp_context7`** for library docs:> - Check `mcp.yaml → context7.default_libraries` for pre-configured libs> - Example: `libraryId: /nuxt/nuxt`, query: "Nuxt 4 composables"## When to use this skill- **Trigger 1**: Description of situation...- **Trigger 2**: Description of situation...- **Anti-pattern**: Do NOT use this skill when...## Decision TreeBefore acting, determine the specific scenario:1. **IF** [Condition A]: - Use `scripts/script_a.py` - Refer to `references/guide_a.md`2. **IF** [Condition B]: - Follow the manual workflow below3. **ELSE**: - Ask user for clarification## Workflow### Phase 1: Preparation1. Verify prerequisites...2. Check for existing files...### Phase 2: Execution> **Tip**: Use `task_boundary` to track progress if this is a long task.1. Step 1...2. Step 2...### Phase 3: Verification1. Run validation checks...2. Notify user...## Iteration Protocol (Ephemeral → Persistent)> [!IMPORTANT]> **Phase 1: Draft in Brain**> - Create drafts as UI Artifacts (in `brain/` conversation directory)> - Iterate with user via `notify_user` until approved> - Keep Q&A and sketches here — do NOT pollute `project/docs/`>> **Phase 2: Persist on Approval**> - ONLY after "Looks good" → write final to `project/docs/` path> - Update file status: `Draft` → `Approved` in header> - The `project/docs/` folder is the ONLY memory that survives sessions## Artifact Ownership- **Creates**: `project/docs/<category>/<artifact>.md`- **Reads**: `<previous skill artifacts>`- **Updates**: `project/docs/ARTIFACT_REGISTRY.md` (status + timestamp)## TDD Protocol> [!CAUTION]> **NO CODE WITHOUT FAILING TEST.**> - **Red**: Write test → Fail.> - **Green**: Write code → Pass.> - **Refactor**: Clean up.> **NEVER write implementation code without a failing test.**> **NEVER fix a bug without a reproduction case.**## Handoff Protocol> [!CAUTION]> **BEFORE delegating to next skill:**> 1. ✅ Final document exists in `project/docs/` (not just brain artifact)> 2. ✅ File header changed from `Draft` to `Approved`> 3. ✅ `project/docs/ARTIFACT_REGISTRY.md` updated to ✅ Done> 4. ✅ User approved via `notify_user`> 5. THEN delegate## Resources- `scripts/`: - `example_script.py`: {{SCRIPT_DESC}}- `references/`: - `reference.md`: {{REF_DESC}}

Frequently asked questions

[object Object]