Person
Eddie
GitHub@secondskylast push
Capabilities
Provides
Agent guidanceBTPAgent guidancePackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.
Entries
Group by
EntrySignals
Maintains
secondsky/sap-skillssecondsky/sap-skillsForty SAP development plugins installed through the skills command line or the Claude Code and Codex marketplaces, with a record per plugin of what its claims were checked against.independent, btp
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
Forty SAP development plugins for coding agents
Details
History
- secondsky/sap-skillsThe type's own block, which this entry predates: a skill carries one key, how it reaches an agent. The README's Quick Start states two routes, `npx skills add secondsky/sap-skills` through the upstream skills command line and a native marketplace command in Claude Code and in Codex, each with its own line quoted. The npx line reads as npm, as [capire/skills](artifact:capire-skills) records the same command shape. Nothing in the README tells a reader to copy or symlink the plugins into a client's configuration folder, so `copy` is left out: absent is not false.
- secondsky/sap-skillsRead today in the two plugins that answer the CAP and the UI5 door, which the ABAP pass had not opened. The sap-cap-capire skill's frontmatter states that it covers Node.js and Java runtimes, so CAP's two flavors rest on the maintainer's sentence where the entry previously answered in both by the serves-another-door fallback, which is the same reading off an absence. The sapui5 skill's frontmatter names freestyle apps and Fiori elements apps in one clause, so freestyle is stated, and fiori-elements moves onto that sentence from the README line about which request activates sap-fiori-tools, which said what triggers a plugin rather than what it covers. Nothing read names UI5 Web Components, so that flavor stays unstated. Stating freestyle changes an answer: the entry answered no there while it stated one UI5 flavor and now answers yes, which a reader comparing that flavor's options will see. The ABAP pair is unchanged.
- secondsky/sap-skillsThe maintainer publishes the plugins on their own site too: the repository's About sidebar names it as the website, and the sap-abap-cds skill carries the same address in its own frontmatter metadata. Proposed on 2026-09-14 and still unaccepted; re-read on 2026-10-15 and unchanged.
- secondsky/sap-skillsThe ABAP-door pass asked what this entry answers in each of that door's two flavors, and both of its ABAP plugins state the answer in their own frontmatter: the sap-abap skill covers classic ABAP and ABAP for Cloud Development, and the sap-abap-cds skill covers ABAP 7.4+ through ABAP Cloud. Each flavor carries the sentence it rests on. Stating both says the same thing the serves-another-door fallback would derive, with the difference that it is now sourced rather than read off an absence. Neither flavor's state on the capability moves: this entry is independent and both flavors already read community-only.
- secondsky/sap-skillsFive of the forty plugins register an MCP server with a pinned version in their .mcp.json; all five files were read on 2026-10-15 at the versions first recorded on 2026-09-14. The 2026-09-14 proposal wrote the qualification into each edge's `for` and left `requirement` unset, which the checker read as an optional relationship on a required edge. Each edge now carries requirement conditional with the condition the README states, which is the form the schema has for a dependency that holds only in some configurations. The README counts "7 with MCP integration"; the other two have no edge, and both files were read on 2026-10-15 to say why rather than assert it. plugins/sap-bw-query/.mcp.json starts powershell.exe on ${CLAUDE_PLUGIN_ROOT}/scripts/Start-BwMcp.ps1, a script inside the plugin, and the sap-sac-scripting skill states that its server "is source-installed, not npm-installed" and gives clone, checkout and build commands for a repository of the maintainer's own.
- secondsky/sap-skillscapability:agent-guidance declares the installs_into property on the BTP and the ABAP door, and this entry sits on both. The Quick Start names six clients in one sentence as current examples of what the upstream skills command line supports, and Claude Code and Codex each have a native marketplace command of their own beside it, the Codex example installing the sap-abap plugin by name. No applies_to scope: the install route is the same whichever plugin a reader wants, so the answer is not a BTP-only or an ABAP-only one. Claude Desktop, Cowork, Kiro and Pi Coding Agent are in the property's vocabulary and no sentence in this README names them, so they are left out: absent is not false.
- secondsky/sap-skillsThe README's Quick Start leads with `npx skills add secondsky/sap-skills` and keeps the two native marketplace commands as further options, so the line that named only the marketplaces described a narrower route than the repository does.
- secondsky/sap-skillsTwo corrections against the README. The repository states that public-source and package-registry evidence is tracked per plugin and that the named ledger file tracks live tenant and system validation, recorded only when evidence exists, which is narrower than one ledger holding all three. The condition belongs to the live validation and not to the registry evidence beside it, which the 2026-10-15 wording left ambiguous, so the sentence now names what the evidence is of. And the opening claimed this was the largest such set in the corpus and the only one treating verification as data, which no source states and the atlas does not rank.
- secondsky/sap-skillsThe same correction as description.what_it_solves, on the edge that carries this artifact's answer to the capability, so the two do not state the repository's evidence model differently. The rewording also removes the two em dashes the prose scan reported in this field.
- secondsky/sap-skillsTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.
- First entry seenDiscovered via sap-ai-mcp-servers.
For your agent
- Ref
actor:secondsky- JSON
- /actors/secondsky.json
- MCP
- Connecting an agent