Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Q6012 Mmic Layout Optimization

ASecurity

Optimize the arrangement of active cells and combining interconnect on a MMIC die by trading die area against thermal spreading against insertion loss, under ECSS-Q-ST-60-12C clause 7.2.10: score each candidate placement, reject the ones that break a channel-temperature ceiling, an area budget or a loss allowance, and keep the best weighted survivor. Use when several cell pitches or die outlines are on the table and one arrangement has to be chosen and defended. Refuses a pitch that walks a c...

2 stars
0 votes
0 copies
0 views
Added 9/27/2026
ai-agentspythonexpressperformance

Works with

claude code

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill q6012-mmic-layout-optimization --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q6012 Mmic Layout Optimization?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Q6012 Mmic Layout Optimization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q6012-mmic-layout-optimization/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q6012-mmic-layout-optimization)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: q6012-mmic-layout-optimization
description: "Optimize the arrangement of active cells and combining interconnect on a MMIC die by trading die area against thermal spreading against insertion loss, under ECSS-Q-ST-60-12C clause 7.2.10: score each candidate placement, reject the ones that break a channel-temperature ceiling, an area budget or a loss allowance, and keep the best weighted survivor. Use when several cell pitches or die outlines are on the table and one arrangement has to be chosen and defended. Refuses a pitch that walks a cell off the die and weights that do not sum to one. Trigger: ecss, q-st-60-12c, mmic-cell-placement-pitch, mmic-thermal-spreading-resistance, mmic-die-area-budget, mmic-combining-interconnect-loss, peak-channel-temperature, mmic-layout-trade."
license: Apache-2.0
compliance: STANDARDS-REF
standards:
  - id: ecss
    reference-only: true
gated: false
domain: space-systems
pack: space-systems
compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"
metadata:
  domain: space-systems
  subdomain: ecss
  tags: [ecss, q-st-60-12-mmic-die-scope, q6012-mmic-layout-optimization, mmic-cell-placement-pitch, mmic-thermal-spreading-resistance, mmic-die-area-budget, mmic-combining-interconnect-loss, peak-channel-temperature]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS MMIC Die -- Layout Arrangement Trade (space-systems/ecss/q6012-mmic-layout-optimization)

Use when the task is the layout step of ECSS-Q-ST-60-12C clause 7.2.10: a MMIC
has several candidate arrangements of its active cells and combining network,
and the question is which placement balances die area, heat spreading and
electrical performance rather than winning one of them outright.

## Domain quick reference

- The placement pitch is the single variable that moves all three metrics at
  once, and it moves them against each other. Opening the pitch spreads the
  heat, so the centre cell runs cooler; it also lengthens the combining run and
  widens the die, so loss and area both rise. That opposition is the trade.
- The hot cell is not the average cell. A centre cell carries its own
  self-heating plus a share of every neighbour's, the share falling off with
  pitch and with how many cells away the neighbour sits, so peak channel
  temperature is what the arrangement is judged on, not the mean rise.
- A constraint and an objective are different instruments. A channel
  temperature ceiling, a die area budget and a loss allowance are pass or fail;
  the weighted score only ranks what already passed. Scoring an arrangement
  that breaks a ceiling produces a winner nobody can build.
- Weights only mean something on normalised metrics. Square millimetres,
  degrees and decibels do not add, so each metric is first expressed as a
  multiple of the best value any surviving candidate achieved for it, and the
  weights are applied to those pure ratios.
- One survivor is a result, not a trade. When constraints leave a single
  feasible arrangement there is nothing to weigh it against, and that is worth
  reporting rather than presenting the survivor as an optimum.

## Workflow

1. Validate each candidate: a name, a cell count, a placement pitch, the die
   outline, the dissipated power and the combining feed. A pitch that walks the
   outermost cell past the die edge is an input error, not a compact layout.
2. Derive the three metrics per candidate: die area from the outline; effective
   thermal resistance of the centre cell from self-heating plus mutual heating;
   peak channel temperature from the baseplate, the per-cell power and that
   resistance; insertion loss from the combining length and the loss per
   millimetre of the technology.
3. Apply every hard constraint, absorbing floating-point representation error
   at the limit with a named tolerance so an exactly-sized candidate is kept,
   and retain each rejected candidate together with the reason it fell.
4. Normalise the surviving candidates metric by metric against the best value
   seen, apply the validated weights, and rank by the weighted score with the
   candidate name breaking ties so the run is reproducible.
5. Report the selection, the full ranking, the rejected candidates with reasons
   and any finding, so the arrangement can be defended and not just named.

## Pitfalls

- Trading on average die temperature. The failure mechanism follows the hottest
  channel, and an arrangement that looks comfortable on the mean can be well
  past its ceiling at the centre cell.
- Treating a ceiling as a heavy weight. Weighting a constraint lets a candidate
  buy its way past a limit with area or loss, which is how an infeasible
  arrangement reaches a review as the recommended one.
- Adding raw metrics. Millimetres squared, degrees and decibels summed directly
  produce a score dominated by whichever unit happens to have the largest
  numbers, and the weights then mean nothing.
- Tightening the pitch to recover die area without re-running the thermal step.
  Mutual heating rises as the pitch closes, so an area saving taken alone is an
  undeclared temperature rise.
- Presenting a lone survivor as the optimum. When only one arrangement cleared
  the constraints the trade was never performed, and a reader needs to be told
  that rather than shown a ranking of one.

## Behavior contract (gate 3)

The candidate validation, the area, thermal-spreading and loss metrics, the
constraint gate, the normalisation and the weighted selection are exercised by
the gate 3 contract test:
scripts/test_q6012_mmic_layout_optimization.py against
scripts/q6012_mmic_layout_optimization_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_q6012_mmic_layout_optimization.py

## Compliance

- ECSS standards are freely downloadable (ESA); cite the source and
  paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.

Attribution

ashfordeOUashfordeOU
View sourceMore from ashfordeOU →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

694821 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →