[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RECTBWK9324YVZMT2JQ9S":3,"skill-same:01M77RECTBWK9324YVZMT2JQ9S":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77RECTBWK9324YVZMT2JQ9S","efcore-d2-db-diagram",null,"Generate D2 database diagrams from Entity Framework Core models. USE FOR: EF Core database diagram, Entity Framework Core ERD, DbContext diagram, C# entity relationship diagram, PostgreSQL schema visualization, generate .d2 file from EF Core entities, Fluent API mapping diagram, migrations-based database diagram, table relationships, owned types, many-to-many join tables, indexes and constraints. DO NOT USE FOR: runtime debugging, database migration execution, schema deployment, SQL performance tuning, or draw.io diagrams.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fefcore-d2-db-diagram\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Generate D2 database diagrams from Entity Framework Core models. USE FOR: EF Core database diagram, Entity Framework Core ERD, DbContext diagram, C# entity relationship diagram, PostgreSQL schema visualization, generate .d2 file from EF Core entities, Fluent API mapping diagram, migrations-based database diagram, table relationships, owned types, many-to-many join tables, indexes and constraints. DO NOT USE FOR: runtime debugging, database migration execution, schema deployment, SQL performance tuning, or draw.io diagrams.\"\n---\n# EF Core D2 Database Diagram Generator\n\n## When to Use\n\nUse this skill when the user wants to generate a database \u002F ERD diagram from an Entity Framework Core codebase.\n\nTypical requests:\n\n- Generate a D2 database diagram from EF Core entities.\n- Visualize tables, columns, primary keys, foreign keys and relationships.\n- Analyze `DbContext`, `DbSet\u003CT>`, `IEntityTypeConfiguration\u003CT>`, Fluent API and migrations.\n- Produce a `.d2` file renderable to SVG\u002FPNG with the `d2` CLI.\n- Document the database model of an ASP.NET Core \u002F .NET project.\n\n## Goal\n\nCreate a readable D2 entity-relationship diagram that reflects the actual EF Core persistence model, not only the raw C# class shape.\n\nThe diagram must prioritize:\n\n1. Database tables and relationships.\n2. Primary keys, foreign keys, required\u002Foptional columns.\n3. Owned types and value objects.\n4. Many-to-many relationships and join tables.\n5. Indexes, unique constraints and table names.\n6. EF Core conventions only when explicit mapping is absent.\n\nOutput is `.d2` source code. It can be rendered to SVG or PNG via the `d2` CLI.\n\n## Tools\n\n- **d2 CLI**: render `.d2` files to SVG\u002FPNG.\n  - `d2 input.d2 output.svg`\n  - `d2 --layout=elk input.d2 output.svg`\n- **d2 fmt**: format D2 files.\n  - `d2 fmt input.d2`\n- No MCP server is required. The skill generates D2 source code as text.\n\n## Recommended Workflow\n\n1. Read the EF Core project structure.\n2. Locate all `DbContext` classes.\n3. Locate all `DbSet\u003CT>` declarations.\n4. Locate entity classes, owned types, enum types and value objects.\n5. Read `OnModelCreating` and all `IEntityTypeConfiguration\u003CT>` classes.\n6. Read migrations when available to confirm table names, join tables, indexes and delete behaviors.\n7. Build a normalized database model before writing D2.\n8. Ask the mandatory diagram questionnaire before generation.\n9. Generate the `.d2` file using the database model, not raw class nesting.\n10. Validate D2 syntax with `d2 fmt` before delivery.\n11. Render with `d2 --layout=elk schema.d2 schema.svg` when possible.\n12. If regenerating, re-read EF Core mappings and migrations first.\n\n## Mandatory Questions Before Diagram Generation\n\nAsk these questions for every new diagram and every regeneration unless the user already answered them in the same request.\n\n1. `Which DbContext should be diagrammed? (auto-detect\u002Fall\u002Fspecific name)`\n2. `Display columns? (all\u002Fkey-only\u002Fnone)`\n3. `Display column types? (Yes\u002FNo)`\n4. `Display nullable\u002Frequired markers? (Yes\u002FNo)`\n5. `Display indexes and unique constraints? (Yes\u002FNo)`\n6. `Display enum values? (Yes\u002FNo)`\n7. `Display owned types? (inline\u002Fseparate\u002Fhide)`\n8. `Display many-to-many join tables? (explicit\u002Fcompact\u002Fhide)`\n9. `Display audit\u002Ftechnical tables? (Yes\u002FNo)`\n10. `Display migration-only tables not present as entities? (Yes\u002FNo)`\n11. `Which grouping mode? (bounded-context\u002Fschema\u002Fnamespace\u002Fflat)`\n12. `Which layout engine? (elk\u002Fdagre\u002Ftala)`\n13. `Which output format? (d2\u002Fsvg\u002Fpng)`\n\nDefault values, when the user asks for a quick generation:\n\n- DbContext: `auto-detect`\n- Columns: `key-only`\n- Column types: `Yes`\n- Nullable markers: `Yes`\n- Indexes: `Yes`\n- Enums: `No`\n- Owned types: `inline`\n- Join tables: `explicit`\n- Audit\u002Ftechnical tables: `No`\n- Migration-only tables: `Yes`\n- Grouping: `bounded-context`\n- Layout: `elk`\n- Output: `d2`\n\n## Reference Documents\n\nLoad these on demand when needed:\n\n| Reference | When to load |\n|---|---|\n| `references\u002Fefcore-model-extraction.md` | Rules for reading DbContext, DbSet, Fluent API, configurations and migrations |\n| `references\u002Fd2-erd-style.md` | D2 syntax and visual conventions for ERD diagrams |\n| `references\u002Frelationship-rules.md` | How to infer one-to-one, one-to-many, many-to-many and owned relationships |\n| `references\u002Fgrouping-modes.md` | Rules for bounded-context, schema, namespace and flat grouping |\n| `references\u002Fquality-gate.md` | Final checklist before delivering the generated diagram |\n\n## EF Core Extraction Rules\n\n### Source Priority\n\nUse this priority order when sources disagree:\n\n1. Latest applied migration \u002F migration snapshot.\n2. Fluent API configuration in `OnModelCreating` or `IEntityTypeConfiguration\u003CT>`.\n3. Data annotations.\n4. EF Core conventions.\n5. Raw C# class shape.\n\n### Required EF Core Concepts to Detect\n\nDetect and represent:\n\n- `DbContext` and `DbSet\u003CT>`.\n- Entity class names and actual table names from `ToTable`.\n- Schema names from `ToTable(\"Table\", \"schema\")`.\n- Primary keys from `HasKey`, `[Key]`, conventions and migrations.\n- Composite keys.\n- Foreign keys from `HasForeignKey`, navigation properties and migration operations.\n- Delete behavior when explicit: `Cascade`, `Restrict`, `NoAction`, `SetNull`, `ClientSetNull`.\n- Required\u002Foptional relationship markers.\n- Owned types from `OwnsOne`, `OwnsMany` and `[Owned]`.\n- Many-to-many relationships from `UsingEntity` and implicit EF Core join tables.\n- Indexes from `HasIndex`, `IsUnique` and migrations.\n- Alternate keys from `HasAlternateKey`.\n- Shadow properties configured in Fluent API.\n- Value conversions when they affect persisted type or readability.\n- Enum properties.\n- Ignored properties and ignored entities.\n\n## Diagram Rendering Rules\n\n### Tables\n\nRepresent each persisted table as a D2 node with `shape: sql_table` when possible.\n\nUse this content convention:\n\n```d2\nClients: {\n  shape: sql_table\n  constraint: primary_key\n  Id: uuid {constraint: primary_key}\n  Name: text\n  Status: enum\n}\n```\n\nIf `sql_table` is unavailable or causes validation issues, fallback to a rectangle with structured text.\n\n### Relationships\n\nUse directional edges from dependent table to principal table.\n\nLabels must include relationship cardinality and FK name when known:\n\n```d2\nOffers.ClientId -> Clients.Id: \"N:1 FK_Offers_Clients_ClientId\"\n```\n\nUse these cardinality labels:\n\n- `1:1`\n- `1:N`\n- `N:1`\n- `N:N`\n- `owned`\n\n### Owned Types\n\nOwned types default to inline rendering.\n\nInline example:\n\n```d2\nClients: {\n  shape: sql_table\n  Id: uuid {constraint: primary_key}\n  Address.Street: text\n  Address.ZipCode: text\n  Address.City: text\n}\n```\n\nIf the user chooses `separate`, represent owned types as visually subordinate tables and use an `owned` relationship.\n\n### Many-to-Many\n\nDefault to explicit join tables because EF Core creates real tables.\n\nFor implicit many-to-many relationships, create a generated join table node and mark it as `implicit join`.\n\n### Technical Tables\n\nHide technical tables by default unless requested.\n\nExamples:\n\n- `__EFMigrationsHistory`\n- Hangfire tables\n- ASP.NET Identity tables\n- Audit logs\n- Outbox tables\n\nIf technical tables are hidden, mention them in the summary after the diagram.\n\n## Grouping Modes\n\n- `bounded-context`: group by detected domain area or folder\u002Fmodule.\n- `schema`: group by database schema, e.g. `public`, `auth`, `billing`.\n- `namespace`: group by C# namespace.\n- `flat`: no containers, all tables at the same level.\n\n## Style Rules\n\nUse consistent styles:\n\n- Primary entity tables: solid border.\n- Join tables: dashed border.\n- Owned types: lighter stroke or nested inline fields.\n- Technical tables: muted style.\n- External tables or migration-only tables: dotted border.\n- Required relationships: solid line.\n- Optional relationships: dashed line.\n- Cascade delete: label suffix `cascade`.\n\n## Quality Gate Before Delivery\n\nBefore delivering the diagram, verify:\n\n- [ ] The selected DbContext is clear.\n- [ ] All `DbSet\u003CT>` entities are considered.\n- [ ] Fluent API configurations are read.\n- [ ] Migrations are checked when present.\n- [ ] Table names and schema names match EF Core mapping.\n- [ ] Primary keys are present.\n- [ ] Foreign keys and cardinalities are represented.\n- [ ] Owned types are handled according to user choice.\n- [ ] Many-to-many join tables are explicit unless the user asked otherwise.\n- [ ] Hidden technical tables are listed in the final summary.\n- [ ] D2 syntax is valid with `d2 fmt`.\n- [ ] Edge endpoints use full dot-notation when inside containers.\n- [ ] The diagram remains readable and avoids crossing-heavy layouts.\n\n## Output Format\n\nWhen the user asks for a skill installation, provide this folder structure:\n\n```text\n.github\u002F\n  skills\u002F\n    efcore-d2-db-diagram\u002F\n      SKILL.md\n      references\u002F\n        efcore-model-extraction.md\n        d2-erd-style.md\n        relationship-rules.md\n        grouping-modes.md\n        quality-gate.md\n```\n\nWhen the user asks to generate a diagram, provide:\n\n1. The `.d2` source file content.\n2. The render command using the selected layout engine.\n3. A concise summary of assumptions and hidden tables.\n","# EF Core D2 Database Diagram Generator\n\n## When to Use\n\nUse this skill when the user wants to generate a database \u002F ERD diagram from an Entity Framework Core codebase.\n\nTypical requests:\n\n- Generate a D2 database diagram from EF Core entities.\n- Visualize tables, columns, primary keys, foreign keys and relationships.\n- Analyze `DbContext`, `DbSet\u003CT>`, `IEntityTypeConfiguration\u003CT>`, Fluent API and migrations.\n- Produce a `.d2` file renderable to SVG\u002FPNG with the `d2` CLI.\n- Document the database model of an ASP.NET Core \u002F .NET project.\n\n## Goal\n\nCreate a readable D2 entity-relationship diagram that reflects the actual EF Core persistence model, not only the raw C# class shape.\n\nThe diagram must prioritize:\n\n1. Database tables and relationships.\n2. Primary keys, foreign keys, required\u002Foptional columns.\n3. Owned types and value objects.\n4. Many-to-many relationships and join tables.\n5. Indexes, unique constraints and table names.\n6. EF Core conventions only when explicit mapping is absent.\n\nOutput is `.d2` source code. It can be rendered to SVG or PNG via the `d2` CLI.\n\n## Tools\n\n- **d2 CLI**: render `.d2` files to SVG\u002FPNG.\n  - `d2 input.d2 output.svg`\n  - `d2 --layout=elk input.d2 output.svg`\n- **d2 fmt**: format D2 files.\n  - `d2 fmt input.d2`\n- No MCP server is required. The skill generates D2 source code as text.\n\n## Recommended Workflow\n\n1. Read the EF Core project structure.\n2. Locate all `DbContext` classes.\n3. Locate all `DbSet\u003CT>` declarations.\n4. Locate entity classes, owned types, enum types and value objects.\n5. Read `OnModelCreating` and all `IEntityTypeConfiguration\u003CT>` classes.\n6. Read migrations when available to confirm table names, join tables, indexes and delete behaviors.\n7. Build a normalized database model before writing D2.\n8. Ask the mandatory diagram questionnaire before generation.\n9. Generate the `.d2` file using the database model, not raw class nesting.\n10. Validate D2 syntax with `d2 fmt` before delivery.\n11. Render with `d2 --layout=elk schema.d2 schema.svg` when possible.\n12. If regenerating, re-read EF Core mappings and migrations first.\n\n## Mandatory Questions Before Diagram Generation\n\nAsk these questions for every new diagram and every regeneration unless the user already answered them in the same request.\n\n1. `Which DbContext should be diagrammed? (auto-detect\u002Fall\u002Fspecific name)`\n2. `Display columns? (all\u002Fkey-only\u002Fnone)`\n3. `Display column types? (Yes\u002FNo)`\n4. `Display nullable\u002Frequired markers? (Yes\u002FNo)`\n5. `Display indexes and unique constraints? (Yes\u002FNo)`\n6. `Display enum values? (Yes\u002FNo)`\n7. `Display owned types? (inline\u002Fseparate\u002Fhide)`\n8. `Display many-to-many join tables? (explicit\u002Fcompact\u002Fhide)`\n9. `Display audit\u002Ftechnical tables? (Yes\u002FNo)`\n10. `Display migration-only tables not present as entities? (Yes\u002FNo)`\n11. `Which grouping mode? (bounded-context\u002Fschema\u002Fnamespace\u002Fflat)`\n12. `Which layout engine? (elk\u002Fdagre\u002Ftala)`\n13. `Which output format? (d2\u002Fsvg\u002Fpng)`\n\nDefault values, when the user asks for a quick generation:\n\n- DbContext: `auto-detect`\n- Columns: `key-only`\n- Column types: `Yes`\n- Nullable markers: `Yes`\n- Indexes: `Yes`\n- Enums: `No`\n- Owned types: `inline`\n- Join tables: `explicit`\n- Audit\u002Ftechnical tables: `No`\n- Migration-only tables: `Yes`\n- Grouping: `bounded-context`\n- Layout: `elk`\n- Output: `d2`\n\n## Reference Documents\n\nLoad these on demand when needed:\n\n| Reference | When to load |\n|---|---|\n| `references\u002Fefcore-model-extraction.md` | Rules for reading DbContext, DbSet, Fluent API, configurations and migrations |\n| `references\u002Fd2-erd-style.md` | D2 syntax and visual conventions for ERD diagrams |\n| `references\u002Frelationship-rules.md` | How to infer one-to-one, one-to-many, many-to-many and owned relationships |\n| `references\u002Fgrouping-modes.md` | Rules for bounded-context, schema, namespace and flat grouping |\n| `references\u002Fquality-gate.md` | Final checklist before delivering the generated diagram |\n\n## EF Core Extraction Rules\n\n### Source Priority\n\nUse this priority order when sources disagree:\n\n1. Latest applied migration \u002F migration snapshot.\n2. Fluent API configuration in `OnModelCreating` or `IEntityTypeConfiguration\u003CT>`.\n3. Data annotations.\n4. EF Core conventions.\n5. Raw C# class shape.\n\n### Required EF Core Concepts to Detect\n\nDetect and represent:\n\n- `DbContext` and `DbSet\u003CT>`.\n- Entity class names and actual table names from `ToTable`.\n- Schema names from `ToTable(\"Table\", \"schema\")`.\n- Primary keys from `HasKey`, `[Key]`, conventions and migrations.\n- Composite keys.\n- Foreign keys from `HasForeignKey`, navigation properties and migration operations.\n- Delete behavior when explicit: `Cascade`, `Restrict`, `NoAction`, `SetNull`, `ClientSetNull`.\n- Required\u002Foptional relationship markers.\n- Owned types from `OwnsOne`, `OwnsMany` and `[Owned]`.\n- Many-to-many relationships from `UsingEntity` and implicit EF Core join tables.\n- Indexes from `HasIndex`, `IsUnique` and migrations.\n- Alternate keys from `HasAlternateKey`.\n- Shadow properties configured in Fluent API.\n- Value conversions when they affect persisted type or readability.\n- Enum properties.\n- Ignored properties and ignored entities.\n\n## Diagram Rendering Rules\n\n### Tables\n\nRepresent each persisted table as a D2 node with `shape: sql_table` when possible.\n\nUse this content convention:\n\n```d2\nClients: {\n  shape: sql_table\n  constraint: primary_key\n  Id: uuid {constraint: primary_key}\n  Name: text\n  Status: enum\n}\n```\n\nIf `sql_table` is unavailable or causes validation issues, fallback to a rectangle with structured text.\n\n### Relationships\n\nUse directional edges from dependent table to principal table.\n\nLabels must include relationship cardinality and FK name when known:\n\n```d2\nOffers.ClientId -> Clients.Id: \"N:1 FK_Offers_Clients_ClientId\"\n```\n\nUse these cardinality labels:\n\n- `1:1`\n- `1:N`\n- `N:1`\n- `N:N`\n- `owned`\n\n### Owned Types\n\nOwned types default to inline rendering.\n\nInline example:\n\n```d2\nClients: {\n  shape: sql_table\n  Id: uuid {constraint: primary_key}\n  Address.Street: text\n  Address.ZipCode: text\n  Address.City: text\n}\n```\n\nIf the user chooses `separate`, represent owned types as visually subordinate tables and use an `owned` relationship.\n\n### Many-to-Many\n\nDefault to explicit join tables because EF Core creates real tables.\n\nFor implicit many-to-many relationships, create a generated join table node and mark it as `implicit join`.\n\n### Technical Tables\n\nHide technical tables by default unless requested.\n\nExamples:\n\n- `__EFMigrationsHistory`\n- Hangfire tables\n- ASP.NET Identity tables\n- Audit logs\n- Outbox tables\n\nIf technical tables are hidden, mention them in the summary after the diagram.\n\n## Grouping Modes\n\n- `bounded-context`: group by detected domain area or folder\u002Fmodule.\n- `schema`: group by database schema, e.g. `public`, `auth`, `billing`.\n- `namespace`: group by C# namespace.\n- `flat`: no containers, all tables at the same level.\n\n## Style Rules\n\nUse consistent styles:\n\n- Primary entity tables: solid border.\n- Join tables: dashed border.\n- Owned types: lighter stroke or nested inline fields.\n- Technical tables: muted style.\n- External tables or migration-only tables: dotted border.\n- Required relationships: solid line.\n- Optional relationships: dashed line.\n- Cascade delete: label suffix `cascade`.\n\n## Quality Gate Before Delivery\n\nBefore delivering the diagram, verify:\n\n- [ ] The selected DbContext is clear.\n- [ ] All `DbSet\u003CT>` entities are considered.\n- [ ] Fluent API configurations are read.\n- [ ] Migrations are checked when present.\n- [ ] Table names and schema names match EF Core mapping.\n- [ ] Primary keys are present.\n- [ ] Foreign keys and cardinalities are represented.\n- [ ] Owned types are handled according to user choice.\n- [ ] Many-to-many join tables are explicit unless the user asked otherwise.\n- [ ] Hidden technical tables are listed in the final summary.\n- [ ] D2 syntax is valid with `d2 fmt`.\n- [ ] Edge endpoints use full dot-notation when inside containers.\n- [ ] The diagram remains readable and avoids crossing-heavy layouts.\n\n## Output Format\n\nWhen the user asks for a skill installation, provide this folder structure:\n\n```text\n.github\u002F\n  skills\u002F\n    efcore-d2-db-diagram\u002F\n      SKILL.md\n      references\u002F\n        efcore-model-extraction.md\n        d2-erd-style.md\n        relationship-rules.md\n        grouping-modes.md\n        quality-gate.md\n```\n\nWhen the user asks to generate a diagram, provide:\n\n1. The `.d2` source file content.\n2. The render command using the selected layout engine.\n3. A concise summary of assumptions and hidden tables.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fefcore-d2-db-diagram",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill efcore-d2-db-diagram",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill efcore-d2-db-diagram",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill efcore-d2-db-diagram","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fefcore-d2-db-diagram\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fd2-erd-style.md","REFERENCE","参考文档",490,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fd2-erd-style.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fefcore-model-extraction.md",927,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fefcore-model-extraction.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fgrouping-modes.md",401,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fgrouping-modes.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fquality-gate.md",516,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Fquality-gate.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Frelationship-rules.md",1010,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fefcore-d2-db-diagram\u002Freferences\u002Frelationship-rules.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]